fix: correct HNSW frontier comparisons in hybrid cache #587
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.

What type of PR is this?
fix: correct HNSW frontier comparisons in hybrid cache
What this PR does / why we need it:
This PR fixes the sign bug in both
func (h *HybridCache) searchLayerHybridandfunc (h *HybridCache) searchLayerHybridWithEarlyStop: the code comparedcurrentDistagainst-results.data[0].disteven though distances were already stored as negatives, so saturated frontiers kept enqueuing worse neighbors instead of pruning them.( the stopping condition
(currentDist > -results.data[0].dist)almost never fires, and the “is this better than the frontier?” check(dist < -results.data[0].dist)is nearly always true.)This prevents needless graph traversal, keeps lookup latency under control, and avoids returning responses routed through poor matches.
semantic-router/src/semantic-router/pkg/cache/hybrid_cache.go
Lines 927 to 951 in f8f042d
Which issue(s) this PR fixes:
Fixes #
Release Notes: Yes/No