[
https://issues.apache.org/jira/browse/NIFI-3163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898598#comment-15898598
]
ASF GitHub Bot commented on NIFI-3163:
--------------------------------------
Github user alopresto commented on the issue:
https://github.com/apache/nifi/pull/1332
I have a question about this process (may be beyond the scope of this PR
though) -- why not allow the DFM to remove the flow.xml.gz from the node with
outdated flow via the REST API and UI from any connected node? The issue is not
limited or blocked connectivity between the nodes, so there could be logic on
the node itself to remove its flow definition when given a properly-authorized
command from a remote node that it knows is connected to the cluster. The
authentication should not be an issue as the DFM permissions should be the same
across the cluster.
I at first considered allowing the node to perform this logic on its own by
archiving its current flow and then deleting it to attempt to rejoin the
cluster, but I can understand how admins would be uncomfortable that the level
of autonomous activity could lead to data loss.
Thoughts?
> 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)
