You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Adrien Grand (JIRA)" <ji...@apache.org> on 2015/09/08 15:20:45 UTC
[jira] [Commented] (LUCENE-6305) BooleanQuery.equals should ignore
clause order
[ https://issues.apache.org/jira/browse/LUCENE-6305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14734785#comment-14734785 ]
Adrien Grand commented on LUCENE-6305:
--------------------------------------
bq. Slightly off topic to your original goal, but what do you think about deduping repeated non scoring (FILTER, MUST_NOT) clauses from the list in the query or do you see that as an possible optimization when building the weights/scorers?
+1 This would be a nice optimization for the rewrite method.
> 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
>
>
> 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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org