Skip to content
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

Jump to bottom

[Protocol] Clarify handling of duplicate add/remove actions #3784

Open
wants to merge 3 commits into
base: master
Choose a base branch
from
+2 −0
Open

[Protocol] Clarify handling of duplicate add/remove actions #3784

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f7177bd
[Protocol] Clarify handling of duplicate add/remove actions
rtyler Oct 19, 2024
16be985
Merge branch 'master' into duplicate_actions_found
rtyler Oct 21, 2024
a907bd4
Merge branch 'master' into duplicate_actions_found
rtyler Oct 23, 2024
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
2 changes: 2 additions & 0 deletions PROTOCOL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -398,6 +398,8 @@ That means specifically that for any commit…
The `dataChange` flag on either an `add` or a `remove` can be set to `false` to indicate that an action when combined with other actions in the same atomic version only rearranges existing data or adds new statistics.
For example, streaming queries that are tailing the transaction log can use this flag to skip actions that would not affect the final results.

A single transaction should not contain duplicate `add` or `remove` actions. Readers may treat such transactions as invalid.

The schema of the `add` action is as follows:

Field Name | Data Type | Description | optional/required
Expand Down
Loading