-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add (optional) sequentialId to StreamElement #206
Closed
Comments
je-ik
added a commit
to datadrivencz/proxima-platform
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
je-ik
added a commit
that referenced
this issue
May 3, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We need to add sequentialId to be able to identify ordering of updates within commit-log, even in the case when they have the same timestamp (or even timestamps swapped).
The sequentialId will be forced to be increasing (and therefore unique) at least within key+attribute pair. It might or might not be increasing over even larger group (e.g. for a whole entity key, for all updates within entity, or even globally).
The tuple (key, attribute, sequentialId) will be representing UUID in case when sequentialId will be part of StreamElement. We will implement this support for InMem and Kafka only (for now).
Part of #198
The text was updated successfully, but these errors were encountered: