[
https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375890#comment-15375890
]
ASF subversion and git services commented on NIFI-1413:
-------------------------------------------------------
Commit 68242d404685d250c166ee0213942037fe8a260d in nifi's branch
refs/heads/master from [~mattyb149]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=68242d4 ]
Revert "NIFI-1413: Ensure that if a node's templates don't match the clusters
that we take the following actions: -Local templates remain but aren't shown in
the cluster's templates. -Any templates from the cluster that don't exist on
the node are added to the node. -Any conflicting template definitions are
replaced by those in the cluster"
This reverts commit 6f6e1b32d98af87c335772fc00089a63b23e7bdf.
> NiFi nodes should not fail to start just because its templates are not
> in-sync with the Cluster.
> ------------------------------------------------------------------------------------------------
>
> Key: NIFI-1413
> URL: https://issues.apache.org/jira/browse/NIFI-1413
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Mark Payne
> Priority: Blocker
> Fix For: 1.0.0
>
>
> If a node tries to join a cluster, the node will fail to join and a
> notification will indicate that the flow on the node is different than the
> cluster's flow, just because the templates are different.
> Rather, we should rename the old template to "<original name>.standalone" or
> something of that nature and then write the template to a new file if it
> conflicts. If the template is simply missing, it should just be downloaded.
> We should make sure that NCM lists only those templates that are available to
> it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
