Skip to content

feat: support per-operation V2 write targets - #8582

Draft
Xuanwo wants to merge 1 commit into
xuanwo/mixed-file-versions-2-validationfrom
xuanwo/mixed-file-versions-3-writes
Draft

feat: support per-operation V2 write targets#8582
Xuanwo wants to merge 1 commit into
xuanwo/mixed-file-versions-2-validationfrom
xuanwo/mixed-file-versions-3-writes

Conversation

@Xuanwo

@Xuanwo Xuanwo commented Aug 17, 2026

Copy link
Copy Markdown
Member

Summary

  • honor explicit exact V2 targets for writes to existing datasets
  • use the manifest storage version only as the operation fallback
  • preserve exact-version behavior through retries, concurrency, and prewritten fragment commits

Stack

  1. feat: add mixed data file version capability #8580 - capability reservation and commit gates
  2. feat: validate mixed V2 data file versions #8581 - capability activation, storage validation, and exact read dispatch
  3. feat: support per-operation V2 write targets #8582 - per-operation write targets
  4. feat: propagate exact V2 versions across dataset operations #8583 - dataset operation propagation
  5. feat: target exact V2 versions in compaction #8584 - compaction targets and binary copy policy
  6. feat: expose exact V2 versions in bindings #8585 - bindings, documentation, and rollout contract

Testing

  • explicit and fallback append targets
  • sequential and concurrent mixed-version writers
  • final-manifest capability derivation and prewritten fragments
  • cargo check and clippy workspace gates

@github-actions github-actions Bot added the enhancement New feature or request label Aug 17, 2026
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from c4eed94 to fbd007f Compare August 18, 2026 18:37
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch 2 times, most recently from 93d9dae to 5a7ef1b Compare August 20, 2026 10:27
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from 5a7ef1b to 6c132df Compare August 20, 2026 13:59
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from 6c132df to 90d301d Compare August 20, 2026 14:15
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from 90d301d to da5e60a Compare August 20, 2026 14:26
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from da5e60a to 65b7002 Compare August 20, 2026 15:15
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from 65b7002 to c108aa3 Compare August 20, 2026 15:22
@Xuanwo
Xuanwo force-pushed the xuanwo/mixed-file-versions-3-writes branch from c108aa3 to abdc835 Compare August 25, 2026 07:50
Xuanwo added a commit that referenced this pull request Aug 27, 2026
## Summary

- reserve bit 256 for mixed V2 data file versions without adding it to
the supported mask
- keep this layer refusing mixed manifests until the per-file storage
contract lands
- add shared commit gates and sticky-capability plumbing needed for safe
activation

## Stack

1. #8580 - capability reservation and commit gates
2. #8581 - capability activation, storage validation, and exact read
dispatch
3. #8582 - per-operation write targets
4. #8583 - dataset operation propagation
5. #8584 - compaction targets and binary copy policy
6. #8585 - bindings, documentation, and rollout contract

## Testing

- cargo test -p lance-table feature_flags
- cargo fmt --all -- --check
- cargo clippy --all --tests --benches -- -D warnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant