Github user joewitt commented on the pull request:
https://github.com/apache/nifi/pull/354#issuecomment-211724253
Oleg off-list pointed out the finer concerns with the member variable.
While it seems pretty far out it also seems like it is accurate. In reading
https://docs.oracle.com/javase/tutorial/essential/concurrency/atomic.html and
https://docs.oracle.com/javase/tutorial/essential/concurrency/memconsist.html
And indeed I cannot think of anything the framework is doing with thread
management or how those lifecycle calls work that would enforce/guarantee a
happens-before relationship for these processor member variables. @markap14
can you?
That said the licensing and thread safety issue of the transform itself are
still needing to be addressed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
