Refactor Qdrant architecture for reusability and maintainability#9
Refactor Qdrant architecture for reusability and maintainability#9google-labs-jules[bot] wants to merge 1 commit into
Conversation
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Refactored the Qdrant client usage to eliminate code duplication and scattered configuration.
Created a new
utils/qdrantdirectory with the following modules:client.py: SingletonQdrantClientManager.config.py: Centralized collection and vector configuration.embeddings.py:EmbeddingServicefor unified model management and caching.operations.py:QdrantOperationsabstraction for common CRUD and search operations.filters.py:FilterBuilderfor constructing complex Qdrant filters.Updated existing files to use these new modules:
utils/knowledge_base/qdrant_retrieval.pyutils/knowledge_base/memory_retrieval.pyutils/knowledge_base/loadvector_qdrant.pyapi/embeddings.pyThis refactoring improves maintainability, connection pooling, and error handling consistency across the application.
PR created automatically by Jules for task 8790263781290474851 started by @NguyenNhat4