[
https://issues.apache.org/jira/browse/NIFI-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424297#comment-15424297
]
ASF GitHub Bot commented on NIFI-2574:
--------------------------------------
Github user joewitt commented on the issue:
https://github.com/apache/nifi/pull/872
@alopresto ok this is now fully up to date with master, full clean build
w/contrib check solid. Standalone app and cluster up and running. There is
some gremlin there still.
@markap14 can you please take a look at this PR/build it and do a simple
GenerateFlowFile -> UpdateAttribute flow and let it run. The UpdateAttribute
won't pull the data from the queue and expiration won't work either. I clearly
missed something. If you could help find the issue that would be wonderful.
@alopresto I think we should get this wrapped up and merged into master and
then NIFI-1831 should be safely layered from that basis.
> Update NiFiProperties usage to a context based accessor rather than static
> singleton
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Configuration, Core Framework
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Labels: migration
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of
> NiFiProperties which enables a loader to exist which will encapsulate all
> logic for dealing with encrypted properties as is the goal of the parent task.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
