rmuir commented on pull request #634: URL: https://github.com/apache/lucene/pull/634#issuecomment-1026805519
The problem is there is no intent telling you where scores are wanted and where they aren't. Specifying this intent (e.g. syntax) is a necessary prerequisite to doing this optimization for `SHOULD` clauses! In your example above, where it's entirely `MUST_NOT` clauses, the optimization is actually safe, because `MUST_NOT` clauses don't impact scoring, since they only restrict matches. So it is fine to optimize this specific case right now. -- 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
