Skip to content

Add a new repeated metadata field for revisions that contain multiple transactions #147

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.

Sign up for GitHub

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

Merged
josephschorr merged 1 commit into from
Sep 9, 2025
Merged

Add a new repeated metadata field for revisions that contain multiple transactions #147

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion authzed/api/v1/watch_service.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,8 @@ message WatchResponse {

// optional_transaction_metadata is an optional field that returns the transaction metadata
// given to SpiceDB during the transaction that produced the changes in this response.
// This field may not exist if no transaction metadata was provided.
// This field may not exist if no transaction metadata was provided, or if multiple pieces
// of metadata were found during the transaction (in which case it is ambiguous which to return).
google.protobuf.Struct optional_transaction_metadata = 3;

// schema_updated, if true, indicates that the schema was changed in this revision.
Expand All @@ -103,4 +104,10 @@ message WatchResponse {
// A checkpoint indicates that the server guarantees that the client
// will not observe any changes at a revision below or equal to the revision in this response.
bool is_checkpoint = 5;

// full_revision_metadata contains all transaction metadata given to SpiceDB during the
// revision that produced the changes in this response. Some datastores (such as CockroachDB)
// can "merge" multiple transactions into a single revision (if the changes occurred concurrently),
// so this field is a list of all transaction metadata seen during the revision.
repeated google.protobuf.Struct full_revision_metadata = 6;
}