Multi branch indexes #68
Merged
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
…uplication - Removed the HybridQueryService and integrated its functionality into RAGQueryService. - Enhanced RAGQueryService to support multi-branch queries, allowing simultaneous searches across target and base branches. - Implemented deduplication logic to prioritize results from the target branch while preserving cross-file relationships. - Updated utility functions to create project-level namespaces for collections. - Improved error handling and logging for collection existence checks and fallback branch logic. - Adjusted semantic search methods to accommodate branch filtering and excluded paths. - Enhanced documentation and comments for clarity on new functionalities and changes.
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces significant refactoring and feature expansion to the RAG (Retrieval-Augmented Generation) branch indexing logic, transitioning from the older "delta index" terminology and architecture to a more general and scalable "multi-branch index" approach. It also removes unused event publishing logic from the branch analysis processor and updates related dependencies.
Key changes include:
Multi-Branch Index Refactor and Feature Expansion
Refactored the
RagOperationsServiceinterface to replace all "delta index" concepts with "multi-branch index" terminology, updating method names, documentation, and logic accordingly. This includes new and renamed methods such asisMultiBranchEnabled,shouldHaveBranchIndex,createOrUpdateBranchIndex,updateBranchIndex,isBranchIndexReady,deleteBranchIndex, andcleanupStaleBranches. The decision record and related logic were also updated toMultiBranchRagDecision. [1] [2] [3] [4]Added new default methods to the
RagOperationsServicefor updating, deleting, and cleaning up branch indexes, providing a more complete multi-branch indexing lifecycle.Codebase Cleanup and Dependency Updates
Updated the import in
BranchAnalysisProcessorto use the new location ofRagOperationsServicefrom the analysis API package, reflecting the architectural decoupling of RAG operations from the engine.Removed the unused
ApplicationEventPublisherdependency and all related event publishing logic (such as analysis started/completed events) fromBranchAnalysisProcessor, simplifying the analysis workflow and reducing unnecessary coupling. [1] [2] [3] [4] [5] [6] [7] [8]Build and Subproject Updates
frontendsubproject commit reference to the latest version.