weaviate.exceptions.WeaviateQueryError: Query call with protocol GRPC search failed with message object search at index

Description

I am using Weaviate Hybrid query and I have nested properties in my schema. I want to pass it to the query_properties in hybrid query but it just gives error

weaviate.exceptions.WeaviateQueryError: Query call with protocol GRPC search failed with message object search at index collection_name: local shard object
search collection_name: Searching by property ‘abc.xyz’ requires inverted index. Is indexSearchable option of property
‘abc.xyz’ enabled? Set it to true or leave empty.

response = collection.query.hybrid(
                query=query_text,
                limit=top_k,
                alpha=alpha,
                return_properties=actual_return_properties,
                return_metadata=metadata_query,
                filters=weaviate_filters,
                query_properties=['a', 'b','abc.xyz']
            )

I have added indexSearchable and still it gives me this error. Is anyone facing the same issue? Any help would be appreciated

hi @Dhruvam !!

Welcome to our community :hugs:

If you note in our docs, there are some limitations for objects datatype:

For instance:

Currently, object and object[] datatype properties are not indexed and not vectorized.

Future plans include the ability to index nested properties, for example to allow for filtering on nested properties and vectorization options.

Let me know if this helps!

1 Like

Oh Thank You!! Just wanted to know if there is any other way to fetch object array datatype values in python. Surely it will help me a lot. Or is there any work around regarding that?

Oh, you can fetch them, but not use the to filter/search, like in query_properties=['a', 'b','abc.xyz']

During creation of nested properties for object array, do i need to mention “skip_vectorisation“ for them or it will take it automatically??

I don’t believe it’s necessary, as it will not be used to vectorize. Maybe in the future it get’s vectorized.

Okay Thank you for your help :smiley:

Hey - we will start vectorizing objects in 1.33 but ONLY if:

  • you are using named vectors (recommended), eg are creating your vectors using wvc.config.Configure.Vectors.XXX
  • explicitly add them via your source properties `wvc.config.Configure.Vectors.text2vec_XXX(source_properties=[“prop1”, “prop2”])`
2 Likes