pgvecto.rs: upgrade pgvecto.rs sdk to v0.2.2 #373
Merged
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.
Here we introduce a bug fix for
PGVecto.rs >= 0.4.0
If we don't need quantization, we pick a
trivial
option at WebUI, and this is the default behavior.In
pgvecto.rs sdk = 0.2.1
, it will be translated into[indexing.ivf.quantization.trivial]
or[indexing.hnsw.quantization.trivial]
as toml config.https://github.com/tensorchord/pgvecto.rs-py/blob/5e175a981b36fbb671033c2db45636a11d6dc04f/tests/__init__.py#L108
But we have a breaking change in
PGVecto.rs 0.4.0
, that it would not accept trivial quantization config. To express no quantization,quantization
should not be showed in config.So
pgvecto.rs sdk = 0.2.2
change the behavior that will translatetrivial
option into[indexing.ivf]
or[indexing.hnsw]
.https://github.com/tensorchord/pgvecto.rs-py/blob/5bc6fc34f2d0df05701000f298596587d58acc99/tests/__init__.py#L108
This is a transparent compile inside SDK, and forward compatibility, so there is nothing to do for VectorDBBench except a upgrade.