[
https://issues.apache.org/jira/browse/NIFI-3300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15849034#comment-15849034
]
ASF subversion and git services commented on NIFI-3300:
-------------------------------------------------------
Commit af2861f1057bc71b450fca883449588a79a7f058 in nifi's branch
refs/heads/master from [~jtstorck]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=af2861f ]
NIFI-3300 Implemented usage of ZooKeeper chroot capability in the connect string
Updated ZooKeeper connect string parsing tests
Updated admin doc for ZooKeeper Migrator migration of nifi root nodes, updated
source and destination ZK check by servers in the connection string instead of
the entire connection string
Added check between source and destination ZooKeeper paths to allow data to be
written to the same ZooKeeper with a different path
Added test for writing to the same ZooKeeper with a different path
Added type parameter to server list in for ZooKeeperEndpointConfig
This closes #1456.
Signed-off-by: Bryan Rosander <[email protected]>
> 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 will require documentation updates in the ZooKeeper Migrator section of
> the System Administration Guide.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
