You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest update to the named vectors, Weaviate added source_properties under the vectorizer configuration, which is GREAT π
Can we move the skip_vectorization from the collection property schema to the vectorizer config (just like this was done with source_properties)? We could call it exclude_properties.
This way, we could deprecate skip_vectorization from the property schema.
Scenarios
Here are a few scenarios (I will provide the examples in Python):
Default β use all relevant properties (existing syntax)
When source_properties or exclude_properties are not provided, Weaviate should use all relevant properties for vectorization.
sebawita
changed the title
[proposal] Move vector property selection under the vectorizer β both include and exclude
[proposal] Vectorizer select and exclude properties β in one place
May 6, 2024
Describe your feature request
Hi team,
With the latest update to the named vectors, Weaviate added
source_properties
under the vectorizer configuration, which is GREAT πCan we move the
skip_vectorization
from the collection property schema to the vectorizer config (just like this was done withsource_properties
)? We could call itexclude_properties
.This way, we could deprecate
skip_vectorization
from the property schema.Scenarios
Here are a few scenarios (I will provide the examples in Python):
Default β use all relevant properties (existing syntax)
Selective (existing syntax)
Exclusive (the new syntax)
Mixed Error
Multiple Vectors
Code of Conduct
The text was updated successfully, but these errors were encountered: