[jira] [Assigned] (NIFI-3300) Zookeeper Migrator should allow importing of data to a new root node

["Jeff Storck (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/NIFI-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Storck reassigned NIFI-3300:
---------------------------------

    Assignee: Jeff Storck

> Zookeeper Migrator should allow importing of data to a new root node
> --------------------------------------------------------------------
>
>                 Key: NIFI-3300
>                 URL: https://issues.apache.org/jira/browse/NIFI-3300
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Tools and Build
>    Affects Versions: 1.1.1
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>            Priority: Minor
>
> ZooKeeper Migrator exports data from ZooKeeper using the absolute path from the root of ZooKeeper.  This prevents the importing of data to a new root node for NiFi, since the path given during the import will have the entire path of the exported data appended to the new root.
> For example, if "/nifi/components" is exported from a ZooKeeper server, the exported data will include the "/nifi/components" path.  When that data is imported to a different ZooKeeper server where the root NiFi node is "/nifi2", and the user imports that data to "/nifi2", nodes will be created under "/nifi2/nifi/components".
> The ZooKeeper Migrator should export data in such a way that, with the given example, the source nodes under "/nifi/components" should be exported without the "/nifi/components" portion of the path, so that those nodes could be imported to the destination root path, such as "/nifi2/components".
> Usage of ZooKeeper client's "chroot" capability should be used in favor of the custom pathing code in the ZooKeeper Migrator.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)