[
https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907964#comment-14907964
]
Adrien Grand commented on LUCENE-6305:
--------------------------------------
I don't think we can order queries in a deterministic way in
BooleanQuery.Builder given that queries are not comparable? So we need the
MultiSet?
I wrote a simple micro-benchmark and was able to create more than 150k
100-clauses boolean queries per second on a single core, which is much faster
than a typical per-core search request throughput. So I don't think we need to
make it optional, we can just enable it all the time?
> 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]
