[
https://issues.apache.org/jira/browse/NIFI-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404686#comment-15404686
]
ASF subversion and git services commented on NIFI-1869:
-------------------------------------------------------
Commit a1bb94c08a82a459341c0a63c4679bd839104c6a in nifi's branch
refs/heads/master from [~bbende]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=a1bb94c ]
NIFI-1869 Cloning controller services when referenced by reporting tasks and
upgrading from 0.x to 1.0.0. This closes #767
> 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
> Assignee: Bryan Bende
> 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)
