[RFC] When to retire the serialization backward compat code for OpenSearch 2.11/2.12/2.13 #5200
Labels
untriaged
Require the attention of the repository maintainers and may need to be prioritized
Comments
github-actions
bot
added
the
untriaged
|
Background: This is related to the "Immutable user object" effort #5168 and intended to make the logic and the code more simple. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In OpenSearch 2.11, a custom serialization mechanism for User objects and other serialized info was introduced. Due to unforeseen issues, it had to be rolled back in OpenSearch 2.14. See #4264 for the change that did the rollback. See #4670 for an example of the issues caused by 2.11/2.12/2.13 .
There is still compatibility code which allows mixed clusters with OpenSearch versions 2.11/2.12/2.13 to co-exist with nodes with newer nodes.
My question is: When can we remove this compatibility mode?
In other words: Which OpenSearch version shall be no longer mixable with 2.11/2.12/2.13? Is it OpenSearch 3?
The text was updated successfully, but these errors were encountered: