Good morning Jennifer. We have been working with NiFi for only a year and so can only offer you that level of "hands on" experience. With that in mind, we established a scripts subdirectory at the same level as the NiFi config, logs, etc. This does mean that we must make migrating that folder part of our upgrade process when we do upgrade, but that does not impose any impediment. And since we link to the latest installation instance through /home/nifi/nifi/latest/[config, logs, scripts, etc etc], we never need to change the script directory location in our ExecuteScript or InvokeScriptedProcessor processors following upgrades.
One other comment: some of the more experienced users had suggested that we not use ExecuteStreamCommand. And in fact I have encountered situations where ExecuteStreamCommand would deep dive into a large file and never return a result or error code. I have no empirical evidence to offer, but we have since heeded that advice and stuck to ExecuteScript and InvokeScriptedProcessor. -Jim On Tue, Apr 11, 2017 at 9:37 AM, Tress, Jennifer L. <jltr...@mitre.org> wrote: > Is there a best practice for where to store scripts used by > ExecuteStreamCommand processors? > > > > > > *Jennifer Tress* > > >
