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
This proposal makes field IDs stable and non-reusable within a dataset branch ancestry by persisting a monotonic allocation high-water mark. New datasets enable the contract by default with required reader and writer feature flags; existing legacy datasets remain unchanged until explicitly migrated.
Please vote with:
+1 approve
0 abstain / no strong opinion
-1 do not approve (please include the blocking concern)
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.
Formal vote on PR #8658.
This proposal makes field IDs stable and non-reusable within a dataset branch ancestry by persisting a monotonic allocation high-water mark. New datasets enable the contract by default with required reader and writer feature flags; existing legacy datasets remain unchanged until explicitly migrated.
Please vote with:
Please keep detailed design discussion in the PR.
All reactions