feat(recall): add opt-in BM25 query term cap#2567
Merged
benfrank241 merged 2 commits intoJul 7, 2026
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
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.
Summary
Fixes #2528 by adding an opt-in cap for PostgreSQL native BM25 query terms.
Native
to_tsquerycurrently OR-joins every normalized query token. For very long recall/consolidation queries, that can produce a huge query that matches too much of a large bank. This addsHINDSIGHT_API_BM25_MAX_QUERY_TERMSso deployments can bound the native tsquery term list.Compatibility notes:
0, which preserves the existing uncapped behavior.Tests
Codex adversarial review: approved after reworking the cap to be opt-in and keeping legacy config/dialect behavior compatible.