Repository navigation
V5 support for transactions #26939
TomaszGaweda
started this conversation in
Ideas
Replies: 1 comment 1 reply
|
@TomaszGaweda I agree on allowing to serialize/deserialize a message id, though we should also define the format for it, to ensure cross-language compatibility. for Regarding the API shape, instead of adding a new interface, I'd do:
|
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi!
Since v5 will be a completely new API, it's a good suggestion to revisit it's support for e.g. transaction, as suggested here.
I'd like to start the discussion by sharing a streaming engine maintainer PoV (I work for Hazelcast on Hazelcast Jet).
Everything is "easy" when everything works ;) But in case of crash or planned restart, we need to ensure everything was committed or rolled back (if we don't recognize such transaction). Therefore, ideal API for streaming engine use case will have:
I am open to contribute necessary changes (or at least help with it). Please let me know if you suggestions make sense and if we should proceed.
Pseudocode:
TxnID- same or very similar to current TxnIDexample usage of listTransactions:
All reactions