[
https://issues.apache.org/jira/browse/NIFI-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15070207#comment-15070207
]
Oleg Zhurakousky commented on NIFI-1289:
----------------------------------------
Actually [~joewitt] I see what you're saying, and I no longer like what I did
(just thinking about what would happen if user executes _getNewInstance_ in
some Processor).
Basically I am going to re-open it and revert the NiFiProperties change and
create a Reflection-based utilities that would allow me to address the issue
strictly for testing and we can push dynamic property conversation for some
other time (unrelated to this issue)
> Inconsistent bootstrapping of nifi.properties
> ---------------------------------------------
>
> Key: NIFI-1289
> URL: https://issues.apache.org/jira/browse/NIFI-1289
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 0.4.0
> Reporter: Oleg Zhurakousky
> Assignee: Oleg Zhurakousky
> Priority: Minor
> Fix For: 0.5.0
>
>
> NiFiProperties caches the 'instance' of properties in a typical Singleton
> fashion.
> This creates issues with tests that provide location of nifi.properties for
> its run when running the entire suite. Fir example when running
> TestStandardProcessScheduler, the first line in setup method:
> {code}
> System.setProperty("nifi.properties.file.path",
> "src/test/resources/nifi.properties");
> {code}
> It is absolutely meaningless when such test is ran as part of the suite
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
