fix: new interface of pgvecto.rs after v0.2 #301
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.
Close #265
This PR migrated to new interface of pgvecto.rs after
v0.2
:l2_ops
->vector_l2_ops
dot_ops
->vector_dot_ops
cosine_ops
->vector_cos_ops
algorithm
->indexing
indexing.ivf.nprob
->indexing.ivf.nsample
vectors
to search_path for schema requirementAnd connect to the new index type:
indexing.ivf
+scaler quantization
at pgvecto.rsApart from that, we fix a requirement bug for pgvector:
sqlalchemy
->psycopg2
How to test it
Please use one of these images to test:
tensorchord/pgvecto-rs:pg16-v0.0.0-nightly.20240410
will be our official v0.3.0 in recent weeks.How to run image
For image
tensorchord/pgvecto-rs:pg16-v0.0.0-nightly.20240410
:Field at Benchmark Webpage
Supported Index types