gsmiller opened a new issue, #11736: URL: https://github.com/apache/lucene/issues/11736
### Description Now that `TermInSetQuery` is able to estimate its cost and work with `IndexOrDocValuesQuery`, it would be nice to have a first-class doc-values-based term-in-set approach to pair with the current postings-based implementation. `DocValuesTermsQuery` in the sandbox module provides this, and I propose we promote the functionality out of `sandbox`. One approach for this, brought up by @rmuir over in #11244, would be to refactor `TermInSetQuery` to extend `MultiTermQuery`. If we do that, we can provide a rewrite method that creates a doc-values-based approach, avoiding some duplicate code. The unknown right now is if extending `MultiTermQuery` would have any adverse performance side-effects on `TermInSetQuery` in general since the terms intersection is implemented a little differently. We would like to benchmark this before making the change. -- 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.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
