fix: backport workflow fixes and btree remap fix to v2.0#5846
fix: backport workflow fixes and btree remap fix to v2.0#5846jackye1995 merged 2 commits intolance-format:release/v2.0from
Conversation
- Change cargo-publish.yml runner from ubuntu-2404-8x-x64 to warp-ubuntu-latest-x64-8x - Add skip_check_repo input to cargo-publish.yml for backfilling missed releases - Fix ref fallback in java-publish.yml checkout steps (use inputs.ref || github.ref) - Fix ref fallback in pypi-publish.yml windows job (use inputs.ref || github.ref) Fixes lance-format#5837 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
) The previous remap implementation assumed it was safe to just copy the lookup unchanged. This is only safe if there are no deletions. If there are deletions then the page boundaries have moved and so the min/max has moved as well. We need to recreate both the lookup and the data when we remap. Closes lance-format#5826
PR ReviewThis backport PR cherry-picks two important fixes to the release/v2.0 branch:
AssessmentThe code changes look correct. The btree remap fix addresses a real bug where the previous implementation only copied lookup files unchanged, which was incorrect when deletions occurred (page boundaries shift, invalidating min/max values). The new approach retrains the index from remapped data, which correctly rebuilds both page data and lookup metadata. Minor observations (non-blocking)
VerdictLGTM ✓ - The backport applies cleanly and the fixes are well-tested. No P0/P1 issues identified. |
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
Summary
Backport to release/v2.0:
Test plan
🤖 Generated with Claude Code