weaviate / weaviate/weaviate-python-client
[Proposal] Create a specific set of exception messages for generative queries
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 227
- Forks
- 151
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 11
Description
Currently, all queries seem to raise a WeaviateQueryError upon failure (e.g. timeouts).
Would it be possible to create a specific exception class & message for any queries from the <collection>.generate submodule? That way we could relay a set of potential troubleshooting messages for RAG queries.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the collection.generate submodule and tracing how failures currently become WeaviateQueryError. Review existing exception and message conventions, then determine the required generate-specific exception behavior and troubleshooting messages; the issue is done when that scope and its tests are defined and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100