mirror of
https://github.com/qdrant/qdrant.git
synced 2026-09-25 07:27:41 -05:00
Arnaud GourlayandClaude Opus 5
00a0e0d768
* test: cover TurboQuant, turbo4 datatype and keyword prefix in compat data Extend the storage compatibility fixture with vector and payload index features that landed since the generator was last updated: * TurboQuant quantization, one collection per persisted blob layout (bits1_5 and the default bits4) * the turbo4 storage datatype, on both dense and multivector storage * the keyword index `prefix` option, plus a matching prefix scroll in the query battery Sparse vector configs reject the turbo4 datatype, so create_collection omits the sparse datatype for that collection rather than forwarding it. This is a no-op for every other collection. Archives are generated once per release and keep the collection set of their own generation, so expected collections are now resolved per version and the new ones are only required from v1.19.0 onward. The prefix scroll stays ungated: archives without the prefix index answer it by scanning. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * test: fail instead of skip when a compatibility archive is missing A 404 from the compatibility bucket means the archive was never published, which no amount of retrying fixes. Skipping it reported the version as covered while nothing ran, so a pull request adding a version could stay green with its new coverage never executing. Fail on 404 and keep skipping connection resets and timeouts, so a bucket outage still does not turn unrelated pull requests red. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
TLS test
Regenerate certificates
- run
PROJECT_ROOT/tests/e2e_tests/test_data/gen.sh - replace old certificates in
PROJECT_ROOT/tests/e2e_tests/test_data/certwith the newly generated ones
Data compatibility test
In order to detect quickly breakage of storage compatibility, we check that the current code understands the storage format from the latest stable release.
To not burden the git repository with tracking the large binary files, we are pushing storage archives to our GCP bucket.
As features are added, the storage format may change. This means updating the reference storage data and snapshot. This is done by running the gen_storage_compat_data.sh script.
Regenerate storage data
Follow those steps to recreate the reference storage data and snapshot.
- run
PROJECT_ROOT/tests/e2e_tests/test_data/compatibility/gen_storage_compat_data.sh - make sure to pick the right version when asked for which system generated the files
- push the new archives to the GCP bucket (ask for the credentials if you don't have them)