valueInt error on cross-reference filters about weaviate HOT 7 CLOSED

Ah, I see what you're driving at! I can reproduce the problem and will look into it. Thanks for raising it 😁

from weaviate.

This has been fixed and merged into stable/v1.23 meaning that it will land in the next patch release.

I will leave the issue open until then. For now, you can unblock yourself by using this image in your local environment: preview-map-correct-dtype-when-filtering-references-by-count-b6ff4ab

from weaviate.

Closing as complete based on the statements above.

from weaviate.

Hi @SavvasMohito, the v4 Python client doesn't use GQL under-the-hood but instead gRPC so they can't be compared.

However, the origin of your problem with the v4 client is due to the way reference filters must be constructed if using the Filter([prop, target, ref_prop]) syntax. With the latest beta release, the filtering syntax has been streamlined so you should be able to perform your query much more easily if you upgrade your client version!

Cheers 😁

from weaviate.

Hi @tsmith023, thanks for your reply. I just tried the latest beta version but am still facing the same issue. The thing is that I am not trying to apply a filter on a value of the cross-reference, I am trying to filter the number of entries a cross-reference has in an object. For example, in my case, I am trying to query GTR_project objects that have at least one occurrence of GTR_spinOut cross-reference (under the hasSpinOut property). And even though I am using an integer filter, the error message that only valueInt filters can be used for what I want to do.

from weaviate.

I think this is the part of weaviate throwing the error, if it helps:

from weaviate.

I appreciate your help @tsmith023. Have a nice day!

from weaviate.