[
https://issues.apache.org/jira/browse/NIFI-2957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651843#comment-15651843
]
ASF GitHub Bot commented on NIFI-2957:
--------------------------------------
GitHub user jtstorck opened a pull request:
https://github.com/apache/nifi/pull/1193
NIFI-2957 ZooKeeper Migration Toolkit
Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
### For all changes:
- [x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
- [x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number
you are trying to resolve? Pay particular attention to the hyphen "-" character.
- [x] Has your PR been rebased against the latest commit within the target
branch (typically master)?
- [x] Is your initial contribution a single, squashed commit?
### For code changes:
- [x] Have you ensured that the full suite of tests is executed via mvn
-Pcontrib-check clean install at the root nifi folder?
- [x] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the LICENSE file, including the main
LICENSE file under nifi-assembly?
- [ ] If applicable, have you updated the NOTICE file, including the main
NOTICE file found under nifi-assembly?
- [ ] If adding new Properties, have you added .displayName in addition to
.name (programmatic access) for each of the new properties?
### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in
which it is rendered?
### Note:
Please ensure that once the PR is submitted, you check travis-ci for build
issues and submit an update to your PR as soon as possible.
Reads from and writes to a Zookeeper that is open or secured via
user/password digest or SASL
Supports persisting of data obtained from Zookeeper to a file or standard
out as JSON
Supports sending of Zookeeper data to Zookeeper from a file or standard out
as JSON
Does not allow data obtained from a source Zookeeper to be written back to
the same Zookeeper connect string and path
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jtstorck/nifi NIFI-2957
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/1193.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 #1193
----
commit 7b7bec120164bb2eb8fb7b0018ad5b5fa4fed6c7
Author: Jeff Storck <[email protected]>
Date: 2016-10-27T16:21:20Z
NIFI-2957 ZooKeeper Migration Toolkit
Reads from and writes to a Zookeeper that is open or secured via
user/password digest or SASL
Supports persisting of data obtained from Zookeeper to a file or standard
out as JSON
Supports sending of Zookeeper data to Zookeeper from a file or standard out
as JSON
Does not allow data obtained from a source Zookeeper to be written back to
the same Zookeeper connect string and path
----
> ZooKeeper migration toolkit
> ---------------------------
>
> Key: NIFI-2957
> URL: https://issues.apache.org/jira/browse/NIFI-2957
> Project: Apache NiFi
> Issue Type: New Feature
> Components: Tools and Build
> Affects Versions: 1.0.0, 0.7.1
> Reporter: Jeff Storck
> Assignee: Jeff Storck
> Fix For: 1.2.0
>
>
> When upgrading from NiFi 0.x to 1.x, or when it is desired to move from the
> embedded ZooKeeper to an external ZooKeeper, state from ZooKeeper needs to be
> migrated.
> Initial considerations:
> * Username/password protection of nodes is not supported in NiFi 1.x.. Those
> nodes that are configured that way in ZooKeeper need to be migrated to have
> an open ACL.
> * The toolkit will support a mode to read data from a configurable root node
> in a source ZooKeeper, and the data will be written to a file designated via
> CLI.
> * The toolkit will support a mode to write data to a destination ZooKeeper
> * The toolkit will not allow data to be written to the same ZooKeeper from
> which the source data was obtained.
> * The toolkit will not support reconnecting to ZooKeeper if it is
> disconnected. The user can rerun the tool.
> * The toolkit will support ZooKeepers configured with Kerberos.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
