lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] [Updated] (LUCENE-2457) QueryNode implementors should override equals method
Date Thu, 09 May 2013 23:06:08 GMT


Uwe Schindler updated LUCENE-2457:

    Fix Version/s:     (was: 4.3)
> QueryNode implementors should override equals method
> ----------------------------------------------------
>                 Key: LUCENE-2457
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: core/queryparser
>            Reporter: Adriano Crestani
>            Priority: Minor
>             Fix For: 4.4
> Discussed on thread:
> "QueryNode(s) are data objects, and it makes sense to override
> their equals method. But before, we need to define what is a QueryNode
> equality. Should two nodes be considered equal if they represent
> syntactically or semantically the same query? e.g. an ORQueryNode created
> from the query <a OR b OR c> will not have the same children ordering as the
> query <b OR c OR a>, so they are syntactically not equal, but they are
> semantically equal, because the order of the OR operands (usually) does not
> matter when the query is executed. I say it usually does not matter, because
> it's up to the Query object implementation built from that ORQueryNode
> object, for this reason, I vote for defining that two query nodes should be
> equals if they are syntactically equal.
> I also vote for excluding query node tags from the equality check, because
> they are not meant to represent the query structure, but to attach extra
> info to the node, which is usually used for communication between
> processors."

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message