Fix: Standardize Weaviate client to v4 API (#218) #221
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Update client.py to use weaviate.connect_to_local() (v4) - Update create_schemas.py to use get_weaviate_client context manager - Remove deprecated v3 API calls (use_async_with_local, connect, close) - Fix mixed API usage causing startup failures (AOSSIE-Org#218)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes backend startup failures caused by mixed Weaviate client APIs (v3 vs v4).
Problem
When setting up the backend locally, contributors encounter runtime errors due to mixed usage of Weaviate client APIs (v3-style imports like
from weaviate import classesvs v4-style APIs likeWeaviateClient).Changes Made
backend/app/database/weaviate/client.py: Updated to use Weaviate v4 API (connect_to_local()instead ofuse_async_with_local())backend/app/database/weaviate/scripts/create_schemas.py: Updated to useget_weaviate_clientasync context managerawait client.connect()andawait client.close()callsTesting
Impact
Backend now starts successfully without Weaviate API conflicts in clean environments.
Closes #218 @smokeyScraper