[
https://issues.apache.org/jira/browse/NIFI-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15109949#comment-15109949
]
Joseph Witt commented on NIFI-1413:
-----------------------------------
or in the case of templates we don't worry about them being different. We
simply make sure the NCM's view of what the right templates are gets copied to
the node. The node may then be a superset of the NCM ones but not a subset.
And we keep moving. They are presently treated like the flow configuration and
that is not strictly necessary.
> 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
> Fix For: 0.6.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)
