Node Distance Reranker: Limit max hops (and cleanup prints) #72
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 includes two changes. First, it limits the maximum number of hops in the node distance reranker. Second, it cleans up unnecessary print statements in the code. These changes improve the efficiency and readability of the code.
Summary:
Limits max hops in
node_distance_reranker
and removes unnecessary print statements for improved efficiency and readability.Key points:
graphiti_core/search/search_utils.py
: Limits max hops to 10 innode_distance_reranker
for optimized search.graphiti_core/llm_client/openai_client.py
: Removes print statement in_generate_response
.graphiti_core/utils/maintenance/edge_operations.py
: Removes print statement inextract_edges
.Generated with ❤️ by ellipsis.dev