[
https://issues.apache.org/jira/browse/NIFI-2767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15992405#comment-15992405
]
ASF GitHub Bot commented on NIFI-2767:
--------------------------------------
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.
> Periodically reload properties from file-based variable registry properties
> files
> ---------------------------------------------------------------------------------
>
> Key: NIFI-2767
> URL: https://issues.apache.org/jira/browse/NIFI-2767
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joey Frazee
> Priority: Minor
>
> Currently FileBasedVariableRegistry only loads properties when it is injected
> into the flow controller so making updates to the properties requires a
> restart.
> Management of data flows would be much easier if these changes could be
> picked up without doing a (rolling) restart. It'd be helpful from an
> administrative standpoint if the FileBasedVariableRegistry reloaded
> properties from the properties files periodically.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
