bug: remove the "not stable yet" warning from DataReplacement commits
Maintainers usually reply within 3 days
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 84/100
Research direction
The warning is in rust/lance-table/src/transaction/manifest_build.rs around lines 1378–1380, inside build_manifest. Read that section and check whether nearby tests cover manifest building with Operation::DataReplacement. Remove the warning and confirm the operation still builds a manifest without logging the unstable warning.
Written by the indexing model from the issue text.
Description
Every commit with Operation::DataReplacement logs a warning from build_manifest:
Building manifest with DataReplacement operation. This operation is not stable yet, please use with caution.
DataReplacement is now used routinely in production, and #9604 makes compaction commit column repacks with it, so every compaction run that repacks columns would log this warning. Nothing else in the codebase marks the operation as unstable. Remove the warning.
- Dominant language
- Rust
- Stars
- 7.2k
- Forks
- 913
- Avg merge
- 4d 19h
- Merged PRs (30d)
- 453
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lance-format/lance
-
bug(docs): headings are confusing on integrations pagesPossibly taken @lance-gatefixer claimed this today. OpenA-docs bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lance-format/lance#10535 ·
Maintainers usually reply within 3 days
-
feature performance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
lance-format/lance#10137 ·
Maintainers usually reply within 3 days
-
Upgrade DataFusion for the unparser stack-overflow fixMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
lance-format/lance#8225 ·
Maintainers usually reply within 3 days
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 84/100
lance-format/lance#6425 · 2 comments ·
Maintainers usually reply within 3 days
-
Expose compute_pq_distanceMay be free again A pull request for this issue was closed without being merged. Openenhancement
Difficulty 1/5 1-3 hours Newbie friendliness 62/100
lance-format/lance#5675 · 1 comment ·
Maintainers usually reply within 3 days
All issues in lance-format/lance
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Y-ASLant/ElegantClipboard#178 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
linxiv-dev/linXiv#384 · 1 comment ·
Maintainers usually reply within 1 day
-
bug drawings ui
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
userFRM/egui-charts#1595 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
smoltcp-rs/smoltcp#1235 ·
Maintainers usually reply within 1 day
-
scope:core type:security
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day