-
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
Design a generic message format for all extensions to ignore unintended bytes. #414
Comments
Coming from #415 there are few ideas which solves the problem. |
So following up on #415 I was able to get a protobuf serialization on top of OpenSearch I've pushed the code changes to my fork and a different branch Here is an example sample message in OpenSearch:
Generate the proto serializer and deserializer: On the extension:
The extension could cleanly de-serialize the message though new extra bytes are sent, it knows how to ignore it.
Extension cleanly accepts partial information and can decide how to proceed.
Sample test from OpenSearch Serialization vs Protobuf on top of OpenSearch Serialization:
From the above example, Protobuf helps:
|
Design a generic message format for all extensions to ignore unintended bytes.
The text was updated successfully, but these errors were encountered: