Monitor Presearcher to reject registration of "ANYTOKEN" queries [LUCENE-10570]
- Dominant language
- Java
- Stars
- 3.6k
- Forks
- 1.4k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 88
Description
I'm starting to do some work with Monitor, and one of the things i realized I was going to want is an easy way to detect Queries that result in `ANYTOKEN` style QueryIndex documents – requiring a "forward search" test against every future `match(Document)` call.
The simplest solution I could come up with is a Presearcher "wrapper" – something that might be generally useful for other users – but I'm certainly open to other approaches.
---
Migrated from [LUCENE-10570](https://issues.apache.org/jira/browse/LUCENE-10570) by Chris M. Hostetter (@hossman), updated Aug 05 2022
Attachments: [LUCENE-10570.patch](https://apache.github.io/lucene-jira-archive/attachments/LUCENE-10570/LUCENE-10570.patch)
Contributor guide
Research direction
Start by reading Monitor's Presearcher flow and the future match(Document) calls described in the issue, then compare the proposed wrapper with the attached LUCENE-10570.patch. Done means Monitor can reject registration of queries that produce ANYTOKEN-style QueryIndex documents without requiring a forward-search check for every match(Document) call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- search
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100