[
https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14736773#comment-14736773
]
Adrien Grand commented on LUCENE-6305:
--------------------------------------
In general I don't like adding such methods because they increase the surface
of our APIs and therefore its complexity. One trade-off I would be ok with
would be to make the multiset lazily computed so that it does not get computed
unless you call equals/hashcode. Would it work for you? If this is not enough,
I tend to agree with Robert that the best option in that case might be to build
a custom query.
> BooleanQuery.equals should ignore clause order
> ----------------------------------------------
>
> Key: LUCENE-6305
> URL: https://issues.apache.org/jira/browse/LUCENE-6305
> Project: Lucene - Core
> Issue Type: Bug
> Reporter: Adrien Grand
> Assignee: Adrien Grand
> Priority: Minor
> Attachments: LUCENE-6305.patch, LUCENE-6305.patch
>
>
> BooleanQuery.equals is sensitive to the order in which clauses have been
> added. So for instance "+A +B" would be considered different from "+B +A"
> although it generates the same matches and scores.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
