[ 
https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735077#comment-14735077
 ] 

Yonik Seeley commented on LUCENE-6305:
--------------------------------------

Cloud this optimization somehow be made optional?
Anyone who is programmatically creating or mutating queries will naturally 
already order clauses.
Also, doing something like adding another clause to an existing boolean query 
will do all the work of ordering yet again.
Perhaps create a subclass for this stuff?

> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to