[
https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701943#comment-14701943
]
Matt Gilman commented on NIFI-826:
----------------------------------
Using name and position works well for components that are positioned. However,
this leaves Connections and Controller Services as components that may not have
a position. Ultimately, this means that a given template could have two
components that are considered equal meaning their configuration is exactly the
same. How do we want to handle this case? Since it's becoming more likely for
an ID conflict to occur, do we still want to prevent the template creation? The
alternative here is that the ordering amongst the two components may change.
The variation isn't ideal but it's ultimately up to the user as they can avoid
the issue if they name the components in question.
Thoughts?
> Export templates in a deterministic way
> ---------------------------------------
>
> Key: NIFI-826
> URL: https://issues.apache.org/jira/browse/NIFI-826
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core Framework
> Reporter: Matt Gilman
> Assignee: Matt Gilman
> Fix For: 0.3.0
>
>
> Templates should be exported in a deterministic way so that they can be
> compared or diff'ed with another. Items to consider...
> - The ordering of components
> - The id's used to identify the components
> - Consider excluding irrelevant items. When components are imported some
> settings are ignored (run state).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
