[
https://issues.apache.org/jira/browse/NIFIREG-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Artem Anokhin updated NIFIREG-243:
----------------------------------
Description:
0) Schema 1
!image-2019-03-27-13-47-25-386.png!
TC:
1) Add ProcessGroup to Workspace
!image-2019-03-27-13-48-15-820.png!
2) We select import ProcessGroup from Nifi-registry
!image-2019-03-27-13-48-35-697.png!
3) Choose one of the versions in which Schema-1 is located.
!image-2019-03-27-13-49-15-651.png!
4) ) After the ProcessGroup is unloaded into the workspace, a new id appears at
the connection (To Input-1, To Input-2, From Output-1, From Output-2
!image-2019-03-27-13-50-29-348.png!
5) Nifi registry captures this as changes in the ProcessGroup
!image-2019-03-27-13-50-51-821.png!
6) And does not allow to switch to the next versions of ProcessGroup
!image-2019-03-27-13-51-03-153.png!
The problem is that I did not make any local changes, but only put the
ProcessGroup in the workspace. But due to the fact that Nifi made a connection
(To Input-1, To Input-2, From Output-1, From Output-2) new id, Nifi-registry
considers local changes made.
was:
0) Schema 1
!image-2019-03-27-13-47-25-386.png!
TC:
1) Add ProcessGroup to Workspace
!image-2019-03-27-13-48-15-820.png!
2) We select import ProcessGroup from Nifi-registry
!image-2019-03-27-13-48-35-697.png!
3) Choose one of the versions in which Schema-1 is located.
!image-2019-03-27-13-49-15-651.png!
4) ) After the ProcessGroup is unloaded into the workspace, a new id appears at
the connection (To Input-1, To Input-2, From Output-1, From Output-2
!image-2019-03-27-13-49-37-675.png!
!image-2019-03-27-13-50-29-348.png!
5) Nifi registry captures this as changes in the ProcessGroup
!image-2019-03-27-13-50-51-821.png!
6) And does not allow to switch to the next versions of ProcessGroup
!image-2019-03-27-13-51-03-153.png!
The problem is that I did not make any local changes, but only put the
ProcessGroup in the workspace. But due to the fact that Nifi made a connection
(To Input-1, To Input-2, From Output-1, From Output-2) new id, Nifi-registry
considers local changes made.
> Impossible to use previous flow version
> ---------------------------------------
>
> Key: NIFIREG-243
> URL: https://issues.apache.org/jira/browse/NIFIREG-243
> Project: NiFi Registry
> Issue Type: Bug
> Reporter: Artem Anokhin
> Priority: Major
> Attachments: image-2019-03-27-13-47-25-386.png,
> image-2019-03-27-13-48-15-820.png, image-2019-03-27-13-48-35-697.png,
> image-2019-03-27-13-49-15-651.png, image-2019-03-27-13-49-37-675.png,
> image-2019-03-27-13-50-29-348.png, image-2019-03-27-13-50-51-821.png,
> image-2019-03-27-13-51-03-153.png
>
>
> 0) Schema 1
> !image-2019-03-27-13-47-25-386.png!
> TC:
> 1) Add ProcessGroup to Workspace
> !image-2019-03-27-13-48-15-820.png!
> 2) We select import ProcessGroup from Nifi-registry
> !image-2019-03-27-13-48-35-697.png!
> 3) Choose one of the versions in which Schema-1 is located.
> !image-2019-03-27-13-49-15-651.png!
> 4) ) After the ProcessGroup is unloaded into the workspace, a new id appears
> at the connection (To Input-1, To Input-2, From Output-1, From Output-2
> !image-2019-03-27-13-50-29-348.png!
> 5) Nifi registry captures this as changes in the ProcessGroup
> !image-2019-03-27-13-50-51-821.png!
> 6) And does not allow to switch to the next versions of ProcessGroup
> !image-2019-03-27-13-51-03-153.png!
>
> The problem is that I did not make any local changes, but only put the
> ProcessGroup in the workspace. But due to the fact that Nifi made a
> connection (To Input-1, To Input-2, From Output-1, From Output-2) new id,
> Nifi-registry considers local changes made.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
