[
https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15329386#comment-15329386
]
ASF GitHub Bot commented on NIFI-826:
-------------------------------------
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/515
@olegz I believe that we're going to need to introduce the templateId or
inceptionId into the flow.xml not just the template DTO. The reasoning is that
we need to support the following case:
Two different systems running the same dataflow should produce the same
serialized XML. In order for this to happen, each component needs to produce
the same UUID and within the collections they need to be ordered the same.
Additionally, we need to only serialize fields that need to be present during
template instantiation.
After template instantiation, they should be able to generate a new
template and the components should still have the same UUIDs, ordered
correctly, and have the correct fields serialized. So that when diffed with the
originally serialized template we would only see the modifications.
> 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: Oleg Zhurakousky
> Fix For: 1.0.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)
