[
https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adrien Grand updated LUCENE-6305:
---------------------------------
Attachment: LUCENE-6305.patch
Revisiting this issue now that queries can be considered immutable. I rebased
the patch to current trunk. BooleanQuery.equals/hashcode don't depend on the
order of clauses anymore but the iteration order of the clauses and the
toString() representation of BooleanQuery have not changed.
> 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 sensible 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]
