-
Notifications
You must be signed in to change notification settings - Fork 34
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
Replace custom invocation id encoding with Protobuf #1478
Comments
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Apr 29, 2024
This commit changes how we store the InvocationId in the partition storage from a custom encoding to using Protobuf. Thereby, we will be able to evolve the InvocationId in the future if needed. This fixes restatedev#1478.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Apr 29, 2024
This commit changes how we store the InvocationId in the partition storage from a custom encoding to using Protobuf. Thereby, we will be able to evolve the InvocationId in the future if needed. This fixes restatedev#1478.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Apr 29, 2024
This commit changes how we store the InvocationId in the partition storage from a custom encoding to using Protobuf. Thereby, we will be able to evolve the InvocationId in the future if needed. This fixes restatedev#1478.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Apr 30, 2024
This commit changes how we store the InvocationId in the partition storage from a custom encoding to using Protobuf. Thereby, we will be able to evolve the InvocationId in the future if needed. This fixes restatedev#1478.
tillrohrmann
added a commit
to tillrohrmann/restate
that referenced
this issue
Apr 30, 2024
This commit changes how we store the InvocationId in the partition storage from a custom encoding to using Protobuf. Thereby, we will be able to evolve the InvocationId in the future if needed. This fixes restatedev#1478.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: