search

weaviate / weaviate

Weaviate is an open-source vector database that stores both objects and vectors, allowing for the combination of vector search with structured filtering with the fault tolerance and scalability of a cloud-native database​.
https://weaviate.io/developers/weaviate/
BSD 3-Clause "New" or "Revised" License
11.53k stars 798 forks source link

Classifications broken with the error 'classification failed: no classes to be classified' #3723

Open evenfrost opened 1 year ago

evenfrost commented 1 year ago

Whenever I try to run a classification, I get an error status:

classification failed: no classes to be classified - did you run a previous classification already?

When I try to delete and recreate all the classes and rerun the classification, I still get the same error. There is also no way to list all the classifications and/or delete the classification (if that's a thing at all). The only way to do is to completely reset and recreate the Weaviate instance, which is not very convenient for sure (and not acceptable in the production environment).

So how can I fix this?

databyjp commented 11 months ago

Hi @evenfrost 👋

A colleague directed me to this example, which works for me. Have you seen this? https://github.com/weaviate/recipes/blob/main/classification/knn/add_data.py

Also, I wonder if your error is related to the class creation process, as I came across the same error when I:

Was this by any chance your workflow as well?

Thank you,

evenfrost commented 11 months ago

Hi @databyjp ,

I think this is the case when a previous classification has failed for any reason, and now every new classification I'm trying to run I'm getting this error.

Restarting Weaviate doesn't help either.

databyjp commented 10 months ago

Oh okay. Would you have a reproducible example that triggers classification to fail, and subsequent ones as well?

stale[bot] commented 8 months ago

Thank you for your contribution to Weaviate. This issue has not received any activity in a while and has therefore been marked as stale. Stale issues will eventually be autoclosed. This does not mean that we are ruling out to work on this issue, but it most likely has not been prioritized high enough in the last months. If you believe that this issue should remain open, please leave a short reply. This lets us know that the issue is not abandoned and acts as a reminder for our team to consider prioritizing this again. Please also consider if you can make a contribution to help with the solution of this issue. If you are willing to contribute, but don't know where to start, please leave a quick message and we'll try to help you. Thank you, The Weaviate Team

moogacs commented 1 month ago

Hi @evenfrost,

from the error you're facing i think you upgraded to 1.25. if you can confirm.

to give some context, there was some regression in 1.25 regarding classification, however that is now resolved and released with v1.25.18. could you upgrade and confirm that the issue doesn't exists more ?

Thanks