You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current codec name string matching check is not sustainable as we move forward with future releases. It doesn't allow for us to support mixed version clusters as it expects the same codec every time.
Additionally, this logic does not support custom codecs (eg: knn plugin uses its custom knn codec that wraps underlying lucene codec).
For a custom codec with the name "customLucene95Codec" and our default codec with name "Lucene95", even though the replica is able to read the custom codec since it uses the same underlying codec - it will not process the checkpoint since the names do not match.
Expected behavior
Moving forward, we want to perform version checks to ascertain if incoming checkpoints can be processed rather than relying on string matching of codec names. By knowing which version we are on, we will also know which lucene codecs it supports.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
OS: [e.g. iOS]
Version [e.g. 22]
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Describe the bug
The current codec name string matching check is not sustainable as we move forward with future releases. It doesn't allow for us to support mixed version clusters as it expects the same codec every time.
Additionally, this logic does not support custom codecs (eg: knn plugin uses its custom knn codec that wraps underlying lucene codec).
For a custom codec with the name "customLucene95Codec" and our default codec with name "Lucene95", even though the replica is able to read the custom codec since it uses the same underlying codec - it will not process the checkpoint since the names do not match.
Expected behavior
Moving forward, we want to perform version checks to ascertain if incoming checkpoints can be processed rather than relying on string matching of codec names. By knowing which version we are on, we will also know which lucene codecs it supports.
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: