gsmiller opened a new pull request, #12089: URL: https://github.com/apache/lucene/pull/12089
### Description This is a DRAFT PR to sketch out the idea of a "self optimizing" TermInSetQuery. The idea is to build on the new `KeywordField` being proposed in #12054, which indexes both postings and DV data. It takes a bit of a different approach though as compared to `IndexOrDocValuesQuery` by "internally" deciding whether to use postings vs. doc values (at the segment granularity). Please note that there are many TODOs in here and I haven't done any benchmarking, etc. I've written light tests to convince myself it works (I've made sure all branches have been exercised), but it's highly likely there are bugs. I'm putting this out there for discussion only. My plan is to benchmark this approach as a next step, but I wanted to float the idea early to see if anyone has feedback or other ideas. Also, if someone loves the idea and wants to run with it, please go for it. I'm pretty busy for the next couple of week and I'm not sure when I'll come back to this. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
