feat(site-call-audit): additive (UpdatedAtUtc, TrackedOperationId) keyset in the reconciliation pull contract
Site side: additive proto after_id field, ReadChangedSinceAsync gains an optional afterId cursor and deterministic (UpdatedAtUtc, TrackedOperationId) ordering — a batch fully inside one UpdatedAtUtc instant no longer re-reads the same page forever. Absent/empty afterId preserves the exact legacy inclusive >= contract, so an older central is unaffected. Regenerated the checked-in gRPC C#.
This commit is contained in:
@@ -171,6 +171,14 @@ message PullAuditEventsResponse {
|
||||
message PullSiteCallsRequest {
|
||||
google.protobuf.Timestamp since_utc = 1;
|
||||
int32 batch_size = 2;
|
||||
// Composite-keyset cursor (Task 15): the TrackedOperationId ("D" GUID form) of
|
||||
// the last row already consumed at since_utc. When set, the site returns only
|
||||
// rows strictly after (since_utc, after_id) under a deterministic
|
||||
// (UpdatedAtUtc, TrackedOperationId) order — un-pinning a batch that would
|
||||
// otherwise stall when more than batch_size rows share one since_utc instant.
|
||||
// Empty (the proto3 string default) preserves the legacy inclusive >= behaviour,
|
||||
// so an older central that never sets it is unaffected. Additive-only.
|
||||
string after_id = 3;
|
||||
}
|
||||
|
||||
message PullSiteCallsResponse {
|
||||
|
||||
Reference in New Issue
Block a user