[jira] [Updated] (NIFI-2432) Clarify message provided when local flow differs from cluster flow

["Joseph Witt (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-2432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joseph Witt updated NIFI-2432:
------------------------------
    Affects Version/s: 1.0.0

> Clarify message provided when local flow differs from cluster flow
> ------------------------------------------------------------------
>
>                 Key: NIFI-2432
>                 URL: https://issues.apache.org/jira/browse/NIFI-2432
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework
>    Affects Versions: 1.0.0
>            Reporter: Mark Payne
>
> Currently, when a node attempts to join a cluster, if its flow is different than the cluster flow, the message provided is not ideal. For example:
> Local Fingerprint:   api.dto.ProcessorDTOPutFileWARN0 secTIMER_DRIVEN1 sec130 secnullConflict Resolution Strategy=replaceCreate Missing Directories=trueDirectory=/home/filePermissions=666NO 
> Cluster Fingerprint: api.dto.ProcessorDTOPutFileWARN0 secTIMER_DRIVEN1 sec130 secnullConflict Resolution Strategy=replaceDirectory=/home/filePermissions=666NO_AUTO_TERMINATED_RELATIONSHIPS6
> From this, one can glean the difference between the flow if they understand the structure of the message, but it is not at all intuitive. At the point when this message is generated, we have both the proposed flow and the current flow. We also have methods that will convert both flows into DTO objects. So we should instead perform a more intelligent 'diff' and output message such as:
> Proposed flow does not contain Process Group ABC(id=1234)
> Proposed flow has different property values for Processor MyPutFile(id=4321):
> Create Missing Directories = true (Local Flow)
> Create Missing Directories = <NO VALUE SET> (Cluster Flow)
> This makes it much more clear what the difference is between the flows so that the admin is able to determine how to address the issue.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)