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

ASF subversion and git services commented on NIFI-11251:
--------------------------------------------------------

Commit 451941aad921f1c15bf65bad8bd58d8a1f7bb62e in nifi's branch 
refs/heads/support/nifi-1.x from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=451941aad9 ]

NIFI-11251: Fixed case in which changing Flow Version was improperly attempting 
to use a Temporary Funnel destination for a connection due to differences in 
Group ID by instead checking if the destination is reachable; fixed issue in 
which processors in an inner versioned group were not stopped even though they 
changed, when a higher-level parent (that was itself under version control) had 
its version changed. Wrote system tests to verify

- Fixed system tests so that they work properly in Clustered version of 
RegistryClientIT
- Fixed system test - ensure that we wait for processors to become valid before 
attempting to start them; also added an additional system test around 
Controller Services in versioned flows

This closes #7095

Signed-off-by: David Handermann <[email protected]>


> Nifi Registry Client with Nested PG - sync issue
> ------------------------------------------------
>
>                 Key: NIFI-11251
>                 URL: https://issues.apache.org/jira/browse/NIFI-11251
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 1.20.0
>            Reporter: Beat Fuellemann
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 2.0.0, 1.21.0
>
>         Attachments: ChangeVersionError.png, FailureRepro.xml
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We upgraded to NIFI 1.20.0 and still have problems with NIFI Registry Client 
> with nested PG. PG and PG Child are both
> commited for versioning NIFI Registry.
> We use NIFI Registry to move NIFI Flows from Staging Environment to the 
> Production via the Registry versioning.
> The problem reliese on on the ExecuteScript Processor.
> How we reproduced the issue:
> On NIFI Instance 1
>  - Create Parent PG "ReproduceSyncProblem"
>  - Create Child PG "InnerProcessGroup"
>  - Add some Processors and add Groovy Script
>  - Commit Child PG "InnerProcessGroup"
>  - commit Parent PG "ReproduceSyncProblem"
> On NIFI Instance 2
>  - import PG from Reqistry into the canvas
>  - do some changes in the Child PG "InnerProcessGroup" -> Change something in 
> the groovy Script
>  - Commit Child PG "InnerProcessGroup"
>  - commit Parent PG "ReproduceSyncProblem"
> on NIFI Instance 1
>  - Update Version on Parent PG "ReproduceSyncProblem"
> -> Expectation: all changes should be done, as well the Child PG changes
> -> ISSUE: ERROR during Change version



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to