gsmiller closed issue #13029: Improve
AbstractMultiTermQueryConstantScoreWrapper#RewritingWeight ScorerSupplier cost
estimation
URL: https://github.com/apache/lucene/issues/13029
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub a
rquesada-tibco commented on issue #13029:
URL: https://github.com/apache/lucene/issues/13029#issuecomment-2150258368
fyi @jboeuf-tibco, @fledigol-tibco
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
msfroh commented on issue #13029:
URL: https://github.com/apache/lucene/issues/13029#issuecomment-2014084615
I get that part of the point of this cost estimate is to avoid the
(potentially-expensive) rewrite if, e.g. we can do a doc-value rewrite instead,
but I'm thinking we could do someth
msfroh commented on issue #13029:
URL: https://github.com/apache/lucene/issues/13029#issuecomment-2014023729
I think the `else` clause for the cost estimate is also not great.
I came across this same problem where a user was essentially running a
single-term `TermInSetQuery` (that ac
rquesada-tibco opened a new issue, #13029:
URL: https://github.com/apache/lucene/issues/13029
### Description
We recently discovered a performance degradation on our project when going
from Lucene 9.4 to 9.9. The cause seems to be a side effect of
https://github.com/apache/lucene/com
