You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@nifi.apache.org by "Oleg Zhurakousky (JIRA)" <ji...@apache.org> on 2016/06/07 19:34:21 UTC
[jira] [Commented] (NIFI-826) Export templates in a deterministic
way
[ https://issues.apache.org/jira/browse/NIFI-826?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15319196#comment-15319196 ]
Oleg Zhurakousky commented on NIFI-826:
---------------------------------------
Had a talk with [~mcgilman] and I amy be splitting this JIRA into two where first one would address the "deterministic" part while the second would address getting rid of elements that should not be serialized in the first place.
As of right now I am playing with the additional immutable ID (as was discussed earlier). I am calling it _inceptionId_ which will be generated only once when specific DTO is created for the first time and will remain unchanged. This id will be utilized in both _hashCode()_ and _equals()_ to ensure proper ordering.
[~mcgilman] [~rpmiskin] - let me know your 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: 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)