[jira] [Commented] (NIFI-826) Export templates in a deterministic way

["Matt Gilman (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15065385#comment-15065385 ] 

Matt Gilman commented on NIFI-826:
----------------------------------

The most recent idea to address the issues laid out was to add an additional ID to each component that would be generated when the component was created initially and would not change regardless how many times it was exported/imported. This would aid in the sorting issue described above. We could also possibly use this ID when updating the connection source/destination IDs prior to exporting.

The components normal ID would be generated when created and every time it was added from a template. This is necessary so the same template could be imported multiple times. However, we address the deterministic issue by using the new ID described above.

> 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
>
> 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)