This section describes Weaviate's individual modules, including their capabilities and how to use them.
- The Vectorizer (also called Retrievers sometimes) modules such as
img2vec-*convert data objects and query inputs to vectors.
- The (Re)Ranker modules such as
rerank-*apply a(n) (additional) ranking process to the search results.
- The Reader & Generator modules process data after retrieving the data from Weaviate, such as to answer questions or summarize text.
- The other modules include everything else, such as a spellcheck module.
Modules can be "vectorizers" (defines how the numbers in the vectors are chosen from the data) or other modules providing additional functions like question answering, custom classification, etc. Modules have the following characteristics:
- Naming convention:
- Vectorizer (Retriever module):
<media>2vec-<name>-<optional>, for example
- Other modules:
<functionality>-<name>-<optional>, for example
- A module name must be url-safe, meaning it must not contain any characters which would require url-encoding.
- A module name is not case-sensitive.
text2vec-bertwould be the same module as
- Vectorizer (Retriever module):
- Module information is accessible through the
- General module information (which modules are attached, version, etc.) is accessible through Weaviate's
- Modules can add
additionalproperties in the RESTful API and
_additionalproperties in the GraphQL API.
- A module can add filters in GraphQL queries.
- Which vectorizer and other modules are applied to which data classes is configured in the schema.
Default vectorizer module
Unless you specify a default vectorization module in Weaviate's configuration, you'll need to specify which vectorization module is used per class you add to the data schema (or you need to enter a vector for each data point you add manually). Set the default with the environment variable
text2vec-contextionary in the Docker Compose file:
Weaviate collections support multiple, named vectors.
Collections can have multiple, named vectors. Each vector is independent. Each vector space has its own index, its own compression, and its own vectorizer. This means you can create vectors for properties, use different vectorization models, and apply different metrics to the same object.
You do not have to use multiple vectors in your collections, but if you do, you need to adjust your queries to specify which vector you want to use.
Backup and restore operations in Weaviate are facilitated by the use of backup provider modules.
These are interchangeable storage backends which exist either internally or externally. The following sections will explain the difference between these two types of backup provider modules, and their intended usages.
External backup providers coordinate the storage and retrieval of backed-up Weaviate data with external storage services.
This type of provider is ideal for production environments. This is because storing the backup data outside of a Weaviate instance decouples the availability of the backup from the Weaviate instance itself. In the event of an unreachable node, the backup is still available.
Additionally, multi-node Weaviate clusters require the use of an external provider. Storing a multi-node backup on internally on a single node presents several issues, like significantly reducing the durability and availability of the backup, and is not supported.
The supported external backup providers are:
Thanks to the extensibility of the module system, new providers can be readily added. If you are interested in an external provider other than the ones listed above, feel free to reach out via our forum, or open an issue on GitHub.
Internal providers coordinate the storage and retrieval of backed-up Weaviate data within a Weaviate instance. This type of provider is intended for developmental or experimental use, and is not recommended for production. Internal Providers are not compatible for multi-node backups, which require the use of an external provider.
As of Weaviate
v1.16, the only supported internal backup provider is the filesystem provider.