You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2023/05/24 17:33:00 UTC
[jira] [Commented] (NIFI-11109) registry client class name modified in flow.json/xml when missing nifi-flow-registry-client-nar
[ https://issues.apache.org/jira/browse/NIFI-11109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17725894#comment-17725894 ]
ASF subversion and git services commented on NIFI-11109:
--------------------------------------------------------
Commit a59ea4a135c5e0caea6710b761c12da9b07750ca in nifi's branch refs/heads/main from NissimShiman
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=a59ea4a135 ]
NIFI-11109 Allow registry client's class in flow.xml/json to not change (#7273)
when underlying nar for nifi-flow-registry-client-nar is missing
> registry client class name modified in flow.json/xml when missing nifi-flow-registry-client-nar
> -----------------------------------------------------------------------------------------------
>
> Key: NIFI-11109
> URL: https://issues.apache.org/jira/browse/NIFI-11109
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.1
> Reporter: Nissim Shiman
> Assignee: Nissim Shiman
> Priority: Major
>
> If nifi is set to use a registry client and nifi-flow-registry-client-nar is removed from lib, the next nifi restart will result in the registry's class name (in flow.xml.gz/flow.json.gz) to be modified from org.apache.nifi.registry.flow.NifiRegistryFlowRegistryClient
> to
> NifiRegistryFlowRegistryClient.
> The url property will also be encrypted.
> When the nifi-flow-registry-client-nar is returned to lib, and nifi is restarted, these changes remain and registry is unreachable using this registry client.
> Update: The remainder of this ticket (that has had its text struck through) has been made into its own ticket (NIFI-11570) as the underlying issue has been found to be different.
> -Also, if the nar removed was nifi-standard-services-api-nar, then besides the above behavior, processors under version control via this registry client may also have their dynamic properties encrypted. These properties remain encrypted even after nifi-standard-services-api-nar is returned to lib and nifi is restarted.-
> -This is seen with a dynamic property added to GenerateFlowFile (when GenericFlowFile is part of a PG under registry version control).-
> -These are edge cases as admins should be very careful about removing nars from lib, but it would be good if protections were added to protect flow.xml/json from modifications in these situations.-
--
This message was sent by Atlassian Jira
(v8.20.10#820010)