Bench/gyst memorybench adapter - #5
Conversation
FTS5 implicit-AND requires every query term to co-occur in one entry, so
natural-language queries miss ('vintage cameras hobby' finds nothing even when
an entry mentions cameras). When the AND match returns zero rows, retry once
with terms OR-joined. Skipped for expressions already containing OR-groups or
operators, so the common case is unchanged.
On the LongMemEval-S 100q subset (sonnet-4.5 judge), this lifts answer accuracy
15.0% -> 65.0% and drops empty-retrieval rate 89% -> 1%. Tradeoff: avg context
tokens rise 293 -> 8695 (OR-mode is lower precision). TDD + 203/203 store tests.
… (H3) The module doc always stated it strips 'did, not, we, it, to, how, why, should', but FTS5_PROBLEM_WORDS omitted the question words/auxiliaries and two tests asserted they remain — contradicting the documented intent. Add question words, pronouns, and non-ambiguous auxiliaries (may/can/will/must excluded as possible content). These rarely appear verbatim in entry text, so dropping them lowers the implicit-AND burden and the noise in the H2 OR-fallback, improving precision. Updated the two doc-contradicting tests; new unit tests cover the contract. 207/207 store tests pass.
…256, models, commit hashes, hardware)
…s-answer split, ceiling)
…ude-judged, subset headline + TODOs)
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (15)
📝 WalkthroughWalkthroughAdds two FTS5 retrieval improvements: an OR-mode fallback in ChangesRetrieval Improvements and Benchmark Documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
What changed
Why
Testing
bun testpassesbun run lintpassesSummary by CodeRabbit
Bug Fixes
Documentation