Skip to main content
Weaviate Docs (migrated from docs.weaviate.io) Docs

Search documentation

Type to search this documentation.

On this pageOverview

Uncompressed vector embeddings

You can opt-out of using vector quantization to compress your vector data.

When creating the collection, you can choose not to use quantization through the collection definition:

Python
from weaviate.classes.config import Configure, Property, DataTypeclient.collections.create(    name="MyCollection",    vector_config=Configure.Vectors.text2vec_openai(        quantizer=Configure.VectorIndex.Quantizer.none()    ),    properties=[        Property(name="title", data_type=DataType.TEXT),    ],)
JS/TS
import weaviate, { configure } from 'weaviate-client';
Java
client.collections.create("MyCollection",    col -> col.vectorConfig(VectorConfig.text2vecTransformers(vc -> vc        .quantization(Quantization.uncompressed())    )).properties(Property.text("title")));
C#
await client.Collections.Create(    new CollectionCreateParams    {        Name = "MyCollection",        Properties = [Property.Text("title")],        VectorConfig = Configure.Vector(            "default",            v => v.Text2VecTransformers(),            index: new VectorIndex.HNSW            {                Quantizer = new VectorIndex.Quantizers.None { },            }        ),    });

Collections can have multiple named vectors. The vectors in a collection can have their own configurations, and compression must be enabled independently for each vector. Every vector is independent and can use PQ, BQ, RQ, SQ, or no compression.

Multi-vector embeddings (ColBERT, ColPali, etc.)

Section titled “Multi-vector embeddings (ColBERT, ColPali, etc.)”

Multi-vector embeddings (implemented through models like ColBERT, ColPali, or ColQwen) represent each object or query using multiple vectors instead of a single vector. Just like with single vectors, multi-vectors support PQ, BQ, RQ, SQ, or no compression.

During the initial search phase, compressed vectors are used for efficiency. However, when computing the MaxSim operation, uncompressed vectors are utilized to ensure more precise similarity calculations. This approach balances the benefits of compression for search efficiency with the accuracy of uncompressed vectors during final scoring.

Have a question or feedback? Here's how to reach us.

Suggest an edit

Propose a replacement for this page. The site team reviews it before applying any changes.

Export
Documentation menu