...
- The original ExecuteProcess (point to a script location)
- ExecuteStreamCommand; sends flowfile content to the standard input stream of the process and transfers standard output back into flowfile content. So your code should read from stdin and write to stdout
- ExecuteSparkInteractive (spark code is set in the processor)
- Some newer "experimental" options
- InvokeScriptedProcessor; you can use Javascript, Groovy, Jython, Lua, or JRuby to create a Processor implementation (code can be in the processor or point to a file)
- ExecuteScript; Clojure, ECMAScript, Groovy, lua, python, ruby (code can be in the processor or point to a file)
- ExecuteGroovyScript (code in the processor)
- InvokeScriptedProcessor; you can use Javascript, Groovy, Jython, Lua, or JRuby to create a Processor implementation (code can be in the processor or point to a file)
"Repositories" Details and Configuration
- https://nifi.apache.org/docs/nifi-docs/html/nifi-in-depth.html
- https://nifi.apache.org/docs/nifi-docs/html/administration-guide.html#flowfile-repository
- https://community.cloudera.com/t5/Community-Articles/Understanding-how-NiFi-s-Content-Repository-Archiving-works/ta-p/249418
HDF/NIFI Best practices for setting up a high performance NiFi installation >> https://community.hortonworks.com/articles/7882/hdfnifi-best-practices-for-setting-up-a-high-perfo.html
...