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

Test if Zoo-prop-editor can set classpath context without the manager running #5198

Open
ddanielr opened this issue Dec 18, 2024 · 1 comment
Labels
bug This issue has been verified to be a bug.
Milestone

Comments

@ddanielr
Copy link
Contributor

Describe the bug
Encountered an issue where zoo-prop-editor was unable to set a classpath context value due to not being able to validate the context.
Was able to finally set the value once the manager was up and running.
Need to test the code and see if this was a coincidence as zoo-prop-editor should function when the entire accumulo-cluster is down.

Versions (OS, Maven, Java, and others, as appropriate):

  • Affected version(s) of this project: [e.g. 1.10.0] 2.1.x

Expected behavior
zoo-prop-editor should be able to set any property value as it is defined as a repair tool to use when accumulo cannot start when an invalid configuration value is present in zookeeper.

@ddanielr ddanielr added the bug This issue has been verified to be a bug. label Dec 18, 2024
@ddanielr
Copy link
Contributor Author

A solution to this may be adding a --force or --skip-validation flag to zoo-prop-editor to allow any property value to be set.

Unsure if it should skip propertyType validation as well. Need to see what validation is performed for classpath contexts.

@ddanielr ddanielr added this to the 2.1.4 milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue has been verified to be a bug.
Projects
None yet
Development

No branches or pull requests

1 participant