Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2104
Your instinct about Compilable is spot-on, it's exactly when I stopped
working this branch :P For ExecuteScript, I'd thought such a processor would be
for quick onTrigger() implementations, and due to multithread issues with
[NIFI-1822](https://issues.apache.org/jira/browse/NIFI-1822) (concurrent tasks)
with various scripting engines, things might get dicey for Compilable engines.
However this would be an excellent enhancement for InvokeScriptedProcessor
(ISP), with the caveat that the engine is also Invocable. I haven't run thru
the list of engines thus far (to include Kotlin) to see what that would look
like, but I have investigated it and for the sake of generality I left it out
of the current code. If we can improve ISP (or even ExecuteScript) by
leveraging Compilable, I am totally on board!
---
