Skip to content

fix: respect segmented scalar index flag#49

Merged
everySympathy merged 1 commit into
mainfrom
segmented-flag-opt-out
Jul 7, 2026
Merged

fix: respect segmented scalar index flag#49
everySympathy merged 1 commit into
mainfrom
segmented-flag-opt-out

Conversation

@everySympathy

Copy link
Copy Markdown
Collaborator

Summary

This fixes a routing bug introduced in #28.

In that PR, we changed BTREE and INVERTED to use Lance's segmented index workflow by default. That was too aggressive: it meant callers who explicitly passed segmented=False would still get the segmented workflow.

That makes the flag misleading, and the behavior should be corrected.

After this change:

  • segmented=True uses the segmented index workflow
  • segmented=False uses the existing partitioned workflow, or Lance's direct scalar index path for unsupported distributed types

I also updated the docs and adjusted the regression test to cover this.

Tests

  • ruff check
  • targeted scalar index tests

@everySympathy everySympathy force-pushed the segmented-flag-opt-out branch from ae3a968 to f5447e4 Compare July 7, 2026 12:11
@everySympathy everySympathy force-pushed the segmented-flag-opt-out branch from f5447e4 to 1654d3d Compare July 7, 2026 12:14
@everySympathy everySympathy merged commit 839b411 into main Jul 7, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant