Yes, you are right, That is what i meant. I haven't played with the sandbox, but the key would be to make sure that the user NiFi uses to run has access and permissions to the resources you are adding to the processor. Executestreamprocessor will have the same issue if the path is wrong or non existent in the server. I would first try to find out what user is used to run nifi (ps -ef would be your friend here). Then i would make sure that that user has access to the path in the console. (Use 'ls -l path') from the home directory. Path in this case would be both the path of the executable, and the path of the working directory (Make sure both are accessible) Lastly, try to execute your script from the command line. Thanks! Regards ... View more

Hey Josh: you could do: SHOW CREATE TABLE mytable; and then look for the keyword LOCATION in the output. When i run that in my sql client, the hdfs path is the next line. You can also look for a line that starts with 'hdfs:// If you want to use this with the information @Aditya Sirna provided, you could have a file with multiple statements like: SHOW CREATE TABLE mytable; SHOW CREATE TABLE mytabl1; SHOW CREATE TABLE mytabl2; and then filter for lines that start with hdfs. I haven't found a way to get JUST the Location of a table. Hope that helps. Thanks! Regards ... View more

Hey Marcel: Something that is helpful sometimes, when trying to troubleshoot why nifi cannot run a process, is dropping into the console of the node that runs the process as the nifi user, and run it from there, to make sure the Nifi User can reach the specific script. In your specific scenario, it looks like nifi has a problem with the working directory. Any reason you are not using executestreamcommand for this? Thanks! Regards ... View more