You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucenenet.apache.org by GitBox <gi...@apache.org> on 2022/12/15 09:10:09 UTC
[GitHub] [lucenenet] chenhh021 opened a new pull request, #783: DisjunctionMaxQuery shouldn't depend on disjunct order for equals checks
chenhh021 opened a new pull request, #783:
URL: https://github.com/apache/lucenenet/pull/783
Fix #779 . The original fix in Lucene relied on its own implementation of multiset, a similar one is ported in this PR.
The changes break the consistence with the behavior of Lucene 4.8, but at least provide a solution for those who meet the same problem.
--
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: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] DisjunctionMaxQuery shouldn't depend on disjunct order for equals checks [lucenenet]
Posted by "paulirwin (via GitHub)" <gi...@apache.org>.
paulirwin commented on PR #783:
URL: https://github.com/apache/lucenenet/pull/783#issuecomment-2436488127
For posterity, this is a port of https://github.com/apache/lucene/pull/110, although there are some significant differences from how it was done there. This also changes the public API surface of DisjunctionMaxQuery's Disjuncts property, which is a breaking change, so I think my vote would be to hold this for a future release. I'm going to put this in the Future milestone unless @NightOwl888 wants me to pull it in for the next beta.
--
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: dev-unsubscribe@lucenenet.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org