You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Matt Gilman (JIRA)" <ji...@apache.org> on 2016/08/01 13:15:20 UTC
[jira] [Updated] (NIFI-1869) ControllerService - flow.xml.gz
conversion
[ https://issues.apache.org/jira/browse/NIFI-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Gilman updated NIFI-1869:
------------------------------
Description:
When loading a flow.xml from a 0.x release, ControllerServices will be scoped at the Controller level. As part of the work for multi-tenant authorization, ControllerServices can be scoped per ProcessGroup. As part of the conversion from 0.x to 1.x these ControllerServices should be automatically moved from the Controller level to the root ProcessGroup level.
This is correct for components in the flow (part of some ProcessGroup). However, this is not correct for ReportingTasks that reference a ControllerService. Currently, their ControllerService will be missing as it's been moved into a ProcessGroup. As part of this conversion, we need to move the ControllerServices that are referenced in the flow but leave the ControllerServices that are referenced by a ReportingTask. If the same ControllerService is referenced in both the flow and a ReportingTask, the service should be copied (and generated a new UUID seeded by the existing identifier to keep the value consistent across a cluster) and all references to the previous identifier should be updated.
was:
When loading a flow.xml from a 0.x release, ControllerServices will be scoped at the Controller level. As part of the work for multi-tenant authorization, ControllerServices can be scoped per ProcessGroup. As part of the conversion from 0.x to 1.x these ControllerServices have been automatically moved from the Controller level to the root ProcessGroup level.
This is correct for components in the flow (part of some ProcessGroup). However, this is not correct for ReportingTasks that reference a ControllerService. Currently, their ControllerService will be missing as it's been moved into a ProcessGroup. As part of this conversion, we need to move the ControllerServices that are referenced in the flow but leave the ControllerServices that are referenced by a ReportingTask. If the same ControllerService is referenced in both the flow and a ReportingTask, the service should be copied (and generated a new UUID seeded by the existing identifier to keep the value consistent across a cluster) and all references to the previous identifier should be updated.
> ControllerService - flow.xml.gz conversion
> ------------------------------------------
>
> Key: NIFI-1869
> URL: https://issues.apache.org/jira/browse/NIFI-1869
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Matt Gilman
> Fix For: 1.0.0
>
>
> When loading a flow.xml from a 0.x release, ControllerServices will be scoped at the Controller level. As part of the work for multi-tenant authorization, ControllerServices can be scoped per ProcessGroup. As part of the conversion from 0.x to 1.x these ControllerServices should be automatically moved from the Controller level to the root ProcessGroup level.
> This is correct for components in the flow (part of some ProcessGroup). However, this is not correct for ReportingTasks that reference a ControllerService. Currently, their ControllerService will be missing as it's been moved into a ProcessGroup. As part of this conversion, we need to move the ControllerServices that are referenced in the flow but leave the ControllerServices that are referenced by a ReportingTask. If the same ControllerService is referenced in both the flow and a ReportingTask, the service should be copied (and generated a new UUID seeded by the existing identifier to keep the value consistent across a cluster) and all references to the previous identifier should be updated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)