Github user jfrazee commented on the issue:
https://github.com/apache/nifi/pull/1015
@trixpan Just rebased it again. Made some minor changes: using
MD5SumMonitor with the watcher now because the last modified monitor wasn't
reliably testable, setting the check schedule to 0 disables it, and cleaned up
the tests.
In the JIRA the question of whether this was safe was brought up. From the
standpoint of will reloading the map in the FileBasedVariableRegistry break
anything core, I think the answer is no (it's only used in EL value lookups),
so, assuming I didn't make anything too buggy, it's safe in that respect. From
the standpoint of will it be possible to build flows that don't behave like the
author was expecting if they expected stuff to be static, the answer is
probably yes.
---
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.
---
