gkatiforis opened a new issue, #11892:
URL: https://github.com/apache/lucene/issues/11892
### Description
The query has several match conditions with fuzziness 2, which makes it
quite expensive. I don't want to search for document relevance or any kind of
scoring, just identify the l
rmuir closed issue #11892: Slow queries (fuzzy) - Score calculation takes too
long
URL: https://github.com/apache/lucene/issues/11892
--
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 com
rmuir commented on issue #11892:
URL: https://github.com/apache/lucene/issues/11892#issuecomment-1296228836
sorry, we aren't working on lucene 8.x anymore. currently we develop on
lucene 10 and backport some changes to lucene 9.x
--
This is an automated message from the Apache Git Service
vigyasharma commented on issue #11676:
URL: https://github.com/apache/lucene/issues/11676#issuecomment-1296297234
One problem with this approach is that it relies on wallTime. `QueryTimeout`
today allows for time agnostic implementations like a counter based timeout.
But checking if we can
dsmiley commented on PR #27:
URL: https://github.com/apache/lucene/pull/27#issuecomment-1296525212
I don't quite care enough to spend the time to move it back. More than
anything, I wanted to get your perspective.
--
This is an automated message from the Apache Git Service.
To respond to
