[
https://issues.apache.org/jira/browse/NIFI-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898882#comment-15898882
]
ASF GitHub Bot commented on NIFI-3163:
--------------------------------------
Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1332
@alopresto It'd be convenient if a node can fix stale flow.xml.gz
automatically and join a cluster by removing its flow.xml.gz and fetch the
latest one from primary node. I think we need to add a nifi.property to enable
that logic (disable by default). As you wrote, that is beyond the scope of this
PR. It may be worth for another JIRA to keep discussion going on.
> Flow Fingerprint should include new RPG configurations
> ------------------------------------------------------
>
> Key: NIFI-3163
> URL: https://issues.apache.org/jira/browse/NIFI-3163
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Koji Kawamura
> Assignee: Koji Kawamura
>
> NiFi calculates fingerprint of a flow.xml using attributes related to data
> processing. Since 1.0.0, some RemoteProcessGroup configurations have been
> added, but not being taken into account for fingerprint.
> These new configurations should be revisited and added accordingly.
> - Transport protocol
> - Multiple target URIs
> - Proxy settings
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
