You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The transaction field updated_fragment_offsets is a list of int32 directly in a protobuf definition. This isn't particularly efficiently encoded, and can make transaction files very large.
This vote adds a new field: map<uint64, bytes> updated_fragment_offset_bitmaps = 10; to replace that one.
These fields are actually only used by the committer of the transaction, and not used by other writers when doing conflict resolution. Because of this, there isn't much risk to changing which field is used. Older writers will still be able to do conflict resolution just as they have before.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
The transaction field
updated_fragment_offsetsis a list of int32 directly in a protobuf definition. This isn't particularly efficiently encoded, and can make transaction files very large.This vote adds a new field:
map<uint64, bytes> updated_fragment_offset_bitmaps = 10;to replace that one.These fields are actually only used by the committer of the transaction, and not used by other writers when doing conflict resolution. Because of this, there isn't much risk to changing which field is used. Older writers will still be able to do conflict resolution just as they have before.
PR: #7432
Beta Was this translation helpful? Give feedback.
All reactions