[
https://issues.apache.org/jira/browse/NIFIREG-77?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313321#comment-16313321
]
Rob Moran commented on NIFIREG-77:
----------------------------------
Described as the "even better solution" in the issue description, I think what
is ultimately needed is a _diff_ feature where a user – from the Registry UI –
can view a side-by-side comparison of any two versions of a resource.
>From the NiFi UI side, the diff view can be repurposed to show when a user
>chooses the _show local changes_ action, and *optionally* when a user submits
>a _change version_ action. I emphasize optionally in case they absolutely know
>they want to change versions and don't need to see a diff.
Perhaps in the NiFi UI, the _show local changes_ action becomes _compare
versions_ which would allow the user to select any two versions (including the
local one if it's modified).
The action – _compare versions_ – would then be used consistently across the
Registry and NiFi UIs and result in the same experience.
> Allow a user to see the changes created by the currently loaded version
> -----------------------------------------------------------------------
>
> Key: NIFIREG-77
> URL: https://issues.apache.org/jira/browse/NIFIREG-77
> Project: NiFi Registry
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Joseph Percivall
> Priority: Critical
>
> As a user, I would like to see the changes that are included in a particular
> version. More specifically, if I'm on an old version and I upgrade to a
> version written by someone else, I have no way to know what changes occurred
> during that version upgrade.
> A simple solution would be to utilize the same logic which displays the
> current differences between local and stored in the registry and use that to
> show the differences between the current version N and version N-1. The user
> could then change between versions to see the changes that happened as part
> of that version.
> An even better solution (from a DFM perspective) would be to be able to see
> the changes within any version (not just the most recent). That way a DFM
> wouldn't have to stop the flow for an extended period of time to view the
> changes/differences in different versions but I think that'd be more work.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)