[
https://issues.apache.org/jira/browse/NIFI-10938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17642752#comment-17642752
]
ASF subversion and git services commented on NIFI-10938:
--------------------------------------------------------
Commit e362ee077fb4c86fcadab6ca951d70d37b1b02b6 in nifi's branch
refs/heads/support/nifi-1.19 from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=e362ee077f ]
NIFI-10937, NIFI-10938, NIFI-10939: When restoring flow from XML, properly
parse XML for registry clients, looking for 'id' tag instead of 'identifier'
tag. Fixed typo in error message about Reporting Task for Registry Clients.
Updated StandardFlowComparator so that we compare sub-process groups' contents
only if the Flow Coordinates are different by more than their version
Signed-off-by: Nathan Gough <[email protected]>
This closes #6752.
> If a Ghost Registry Client is created, the message indicates that the
> Reporting Task type is invalid
> ----------------------------------------------------------------------------------------------------
>
> Key: NIFI-10938
> URL: https://issues.apache.org/jira/browse/NIFI-10938
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Mark Payne
> Priority: Trivial
> Fix For: 1.20.0, 1.19.1
>
>
> When I removed the NAR for a particular Registry Client and restarted, NiFi
> started up properly, created a ghosted component for the client. However, the
> error message indicated that the type of the Reporting Task was invalid,
> instead of the type of the Registry Client.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
