add section on event ordering for materialize #403
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@kbrwn is attempting to deploy a commit to the authzed Team on Vercel. A member of the Team first needs to authorize it. |
vroldanbet
requested changes
Oct 30, 2025
Contributor
vroldanbet
left a comment
vroldanbet
left a comment
There was a problem hiding this comment.
One remark, otherwise looks good to me
| Materialize guarantees at-least-once delivery and preserves the order of revisions exactly as emitted by SpiceDB. Revisions will not arrive out of order. However, events within a single revision may appear in any order, since their intra-revision ordering is not semantically significant. | ||
|
|
||
| - **"Revision completed" indicates prior events have been received** | ||
| All events for a given revision will be emitted before the corresponding `"revision completed"` event is sent. If strict ordering of events within a revision is required, client-side ordering logic must be implemented. |
Contributor
There was a problem hiding this comment.
Ordering of events of a revision is semantically irrelevant, I think that was made clear in the previous point, so it seems confusing to mention that the client should take care of this
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds section under the WatchPermissionSets heading to explain how event ordering works in Materialize.