-
Notifications
You must be signed in to change notification settings - Fork 58
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
[BUG] IllegalArgumentException in AD Settings registration #792
Comments
This is due to the stale 3.0.0 latest build in use for AD testing, which does not have the change to the Normally enums in Java are type safe and re-orderable, but in the case of settings sent over transport, the stream uses This SDK bug will self-resolve when the 3.0.0 tarball build gets fixed, but I'm thinking that this change in enum values could definitely have some impact in versioning and backwards compatibility (possibly in 2.8.0 vs. 2.7.0?) @saratvemulapalli and @cwperks do you think we should consider moving that new |
@dbwiddis Is there a way we can synthetically reproduce this in a unit test to show a fix working by adding this to the end of the enum? |
just implement writeable and do a writeTo ... that gives you a byte array with the enum ordinals |
The current bug is that a NodeScope setting with the "old" enum value now gets deserialized as an ExtensionScope. |
Fixed in opensearch-project/OpenSearch#7871 |
What is the bug?
How can one reproduce the bug?
Start up AD feature/extensions branch and init with connection to OpenSearch
What is the expected behavior?
No exceptions
The text was updated successfully, but these errors were encountered: