Skip to content

Vector index: the engine now builds a hierarchy by default; docs and one test say so - #419

Merged
tae898 merged 2 commits into
mainfrom
fix/vector-hierarchy-default-26.12.1
Nov 21, 2026
Merged

tae898 merged 2 commits into
mainfrom
fix/vector-hierarchy-default-26.12.1

Conversation

@tae898

@tae898 tae898 commented Nov 21, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #418

The engine (ArcadeData/arcadedb#12616, release 26.12.1) now builds a hierarchy for a new LSM vector index by default, so a SQL CREATE INDEX ... LSM_VECTOR without "addHierarchy" agrees with create_vector_index(); only quantization still differs. This changes:

  • docs/modules/ROOT/pages/how-to/vectors.adoc: the defaults table (the engine default is true from 26.12.1 and false on 26.11.1 and earlier), the printed output of block 2 (NONE True), and the sentence on how to get the statement's index from the method;
  • the docstring of create_vector_index;
  • tests/test_vector_sql.py and tests/test_docs_vectors_page.py: the same two tests also run in the installed-wheel parity job, on a wheel with engine 26.11.1 (DEV_ENGINE: 26.11.1), which still builds a flat graph from SQL. They now read the engine version through SELECT version(), as test_docs_facets_page.py does, and expect the default of the engine they run on; the page keeps showing the 26.12.1 value. The first version of this pull request asserted the new default everywhere and failed that parity job.

Checked: compile() on the two Python files, uvx pre-commit run --files on the three files (black, isort, ruff and the name check pass). I did not run the two tests locally: they need a wheel built on the snapshot engine, so the platform jobs of this pull request are the check. The two tests are the ones that failed on #417.

…cs and one test say so

ArcadeData/arcadedb#12616 (engine 26.12.1) makes new LSM vector indexes hierarchical by default. A SQL CREATE INDEX without addHierarchy now agrees with create_vector_index(), and only quantization still differs. The how-to page, the docstring of create_vector_index and test_add_hierarchy_default_agrees_between_sql_and_python name the old default (a flat graph) and failed on the snapshot engine since 2026-11-20, which turns the platform tests of every pull request red.

The page says the old default for 26.11.1 and earlier. Closes #418
…s on

The same two tests run on the snapshot engine (a hierarchy by default since ArcadeData/arcadedb#12616) and, in the installed-wheel parity job, on a wheel with engine 26.11.1 (a flat graph from SQL). They now read the engine version through SELECT version(), as test_docs_facets_page.py does, and expect the default of that engine; the page keeps showing the 26.12.1 value.
@tae898
tae898 merged commit 740df36 into main Nov 21, 2026
44 checks passed
@tae898
tae898 deleted the fix/vector-hierarchy-default-26.12.1 branch November 21, 2026 15:56
@github-actions github-actions Bot added this to the 26.12.1 milestone Nov 21, 2026
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.

CI is red on every pull request since 2026-11-20: the engine now builds hierarchical vector indexes by default

1 participant