Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose a --migrate-processor-state cli flag so that it can be used outside of dataflows deployed by flowlib #64

Open
dbkegley opened this issue Oct 22, 2019 · 0 comments

Comments

@dbkegley
Copy link
Contributor

It would be nice to provide a --migrate-processor-state flag for the cli so that we can use this command without deploying a flow. For example if you just want to migrate state from one nifi instance to a new instance for a single processor.

For example: --migrate-processor-state --nifi-endpoint http://nifi:8080 --zookeeper-connection zookeeper:2181 --zookeeper-root-node /nifi --old <old-processor-uuid> --new <new-processor-uuid>

This would read the state if from the provided nifi-endpoint and serialize the k,v pairs into their binary representation. Then it should set the value of the zookeeper node /nifi/components/<new-processor-uuid> as the value of the serialized state.

@dbkegley dbkegley self-assigned this Oct 22, 2019
@dbkegley dbkegley changed the title Expose a --migrate-processor-state cli flag so that it can be used outside of flowlib Expose a --migrate-processor-state cli flag so that it can be used outside of dataflows deployed by flowlib Oct 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant