This repository was archived by the owner on Nov 21, 2026. It is now read-only.
Repository navigation
Docs: say why quantization="PRODUCT" is not recommended - #395
Merged
Merged
Conversation
Explain the reason in the database API page, the vectors guide and the create_vector_index docstring: current engine builds score SQL search candidates with full-precision vectors, write PQ codes that nothing reads, and ignore pqTrainingLimit (ArcadeDB ArcadeData#10514). Refs #394 Co-Authored-By: Claude Haiku 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The docs said
"PRODUCT"/PQ is not recommended but not why. This PR states the reason indocs/api/database.md(thequantizationandpq_training_limitbullets),docs/guide/vectors.mdand thequantizationdocstring ofcreate_vector_indexincore.py: current engine builds score SQL search (vectorNeighbors) candidates with full-precision vectors, so PQ gives no search speedup; the index files are larger than withNonebecause PQ codes are written that nothing reads; andpqTrainingLimitis ignored. Docs and docstring only, no code change.Closes #394
Checks run locally:
uv run --no-project --with pre-commit pre-commit run --fileson the three changed files (all applicable hooks passed; the commit hook run passed too);uv run --no-project ... mkdocs build --strict -f bindings/python/mkdocs.yml(passed, unpinned docs deps, not the pinned CI versions). The docstring-only change needs no test run; the code-block tests were not run because no code block changed.🤖 Generated with Claude Code