Deprecate semantic guided retriever#239
Conversation
|
Lexical Graph Coverage Report: The coverage is at unknown% (target: unknown%). Download the HTML report here. |
|
Lexical Graph Coverage Report: The coverage is at 46.56% (target: 80%). Download the HTML report here. |
|
Lexical Graph Coverage Report: The coverage is at 46.56% (target: 80%). Download the HTML report here. |
Removed an unnecessary blank line for cleaner code.
|
Lexical Graph Coverage Report: The coverage is at unknown% (target: unknown%). Download the HTML report here. |
|
Lexical Graph Coverage Report: The coverage is at unknown% (target: unknown%). Download the HTML report here. |
|
Lexical Graph Coverage Report: The coverage is at 46.03% (target: 80%). Download the HTML report here. |
|
can you add a tests to check deprecation logic? |
|
Lexical Graph Coverage Report: The coverage is at 46.03% (target: 80%). Download the HTML report here. |
Summary
Moves semantic-guided retriever classes into a
deprecated/sub-package with deprecation warnings. Existing imports continue to work but emitDeprecationWarning.Rationale
The semantic-guided search approach requires maintaining a dedicated
statementvector index, which adds storage cost and indexing overhead. The traversal-based search achieves equivalent or better results using only thechunkindex.Migration Guide
from graphrag_toolkit.lexical_graph.retrieval.retrievers import SemanticGuidedRetrieverCompositeTraversalBasedRetrieverfrom graphrag_toolkit.lexical_graph.retrieval.retrievers import SemanticGuidedChunkRetrieverCompositeTraversalBasedRetrieverLexicalGraphQueryEngine.for_semantic_guided_search()LexicalGraphQueryEngine.for_traversal_based_search()What still works (backward compat)
__getattr__lazy loading)DeprecationWarningis emitted on first useRemoval timeline
Targeted for removal in the next major version. Users should migrate before then.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.