[jira] [Commented] (NIFI-1869) ControllerService - flow.xml.gz conversion

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15403283#comment-15403283 ] 

ASF GitHub Bot commented on NIFI-1869:
--------------------------------------

GitHub user bbende opened a pull request:

    https://github.com/apache/nifi/pull/767

    NIFI-1869 Cloning controller services when referenced by reporting ta…

    …sks and upgrading from 0.x to 1.0.0

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bbende/nifi NIFI-1869

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/nifi/pull/767.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #767
    
----
commit 3d5a7fe81f31a30e4e31ade9eff4481b86dbbf36
Author: Bryan Bende <bb...@apache.org>
Date:   2016-08-01T21:50:13Z

    NIFI-1869 Cloning controller services when referenced by reporting tasks and upgrading from 0.x to 1.0.0

----


> 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)