[
https://issues.apache.org/jira/browse/NIFI-11047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julien G. updated NIFI-11047:
-----------------------------
Description:
There is a bug/issue when upgrading a dataflow that was referencing an external
service. In the dataflow, I'm referencing an external service (a service in
higher scope, at the root).
But if in a new version I stop referencing it, when upgrading the dataflow, the
service will still be referenced. So the dataflow will be marked as modified.
Scenario to reproduce (that can be reproduced in 1.16.3 and 1.19.1):
# Create a {{*StandardProxyConfigurationService*}} at the root level
# Create a process group
# In the process group, create a {{*PutGCSObject* processor.}}
# In the processor attach the {{*StandardProxyConfigurationService*}}
# Create a {{*GCPCredentialsControllerService* at the process group level}}
# Attach the {{*GCPCredentialsControllerService* to the processor}}
# Attach the {{*StandardProxyConfigurationService* to the
*GCPCredentialsControllerService*}}
# Version the dataflow
# Remove the referenced {{*StandardProxyConfigurationService* in the processor
and the service}}
# Commit a new version
# Rollback to version 1
# Upgrade to version 2
When in this state, you can't rollback the change. To unstuck the versionning
you need to remove the referenced *{{StandardProxyConfigurationService}}* in
the processor and the service manually to be up to date.
was:
There is a bug/issue when upgrading a dataflow that was referencing an external
service. In the dataflow, I'm referencing an external service (a service in
higher scope, at the root).
But if in a new version I stop referencing it, when upgrading the dataflow, the
service will still be referenced. So the dataflow will be marked as modified.
Scenario to reproduce (that can be reproduced in 1.16.3 and 1.19.1):
# Create a {{*StandardProxyConfigurationService*}} at the root level
# Create a process group
# In the process group, create a {{*PutGCSObject* processor.}}
# In the processor attach the {{*StandardProxyConfigurationService*}}
# Create a {{*GCPCredentialsControllerService* at the process group level}}
# Attach the {{*GCPCredentialsControllerService* to the processor}}
# Attach the {{*StandardProxyConfigurationService* to the
{{*GCPCredentialsControllerService*}}}}
# Version the dataflow
# Remove the referenced {{*StandardProxyConfigurationService* in the processor
and the service}}
# Commit a new version
# Rollback to version 1
# Upgrade to version 2
When in this state, you can't rollback the change. To unstuck the versionning
you need to remove the referenced *{{StandardProxyConfigurationService}}* in
the processor and the service manually to be up to date.
> Issue when upgrading version of dataflow with external service
> --------------------------------------------------------------
>
> Key: NIFI-11047
> URL: https://issues.apache.org/jira/browse/NIFI-11047
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 1.19.1
> Reporter: Julien G.
> Priority: Major
>
> There is a bug/issue when upgrading a dataflow that was referencing an
> external service. In the dataflow, I'm referencing an external service (a
> service in higher scope, at the root).
> But if in a new version I stop referencing it, when upgrading the dataflow,
> the service will still be referenced. So the dataflow will be marked as
> modified.
> Scenario to reproduce (that can be reproduced in 1.16.3 and 1.19.1):
> # Create a {{*StandardProxyConfigurationService*}} at the root level
> # Create a process group
> # In the process group, create a {{*PutGCSObject* processor.}}
> # In the processor attach the {{*StandardProxyConfigurationService*}}
> # Create a {{*GCPCredentialsControllerService* at the process group level}}
> # Attach the {{*GCPCredentialsControllerService* to the processor}}
> # Attach the {{*StandardProxyConfigurationService* to the
> *GCPCredentialsControllerService*}}
> # Version the dataflow
> # Remove the referenced {{*StandardProxyConfigurationService* in the
> processor and the service}}
> # Commit a new version
> # Rollback to version 1
> # Upgrade to version 2
> When in this state, you can't rollback the change. To unstuck the versionning
> you need to remove the referenced *{{StandardProxyConfigurationService}}* in
> the processor and the service manually to be up to date.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
