lucene-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Klaas <>
Subject Re: operator precedence and confusing result
Date Wed, 18 Mar 2009 01:10:21 GMT

On 13-Mar-09, at 11:33 AM, Ted Dunning wrote:

> Actually, the nesting of BooleanQueries with required, optional and  
> excluded
> clauses are equivalent in power to (), AND, OR and AND-NOT.  Any  
> expression
> in one form can be expressed in the other.  Moreover, the Lucene  
> form allows
> very nice intepretation with relevance scoring that is difficult  
> with the
> normal Boolean expressions.
> The only thing you need to have is an accurate translation.  No need  
> to
> remove anything.

Yes, but until that work is done (and it probably belongs in a  
separate queryparser module, imo), we're left with the current  
situation, which doesn't work but seductively gives the appearance of  

Anyway, the point seems moot given the volumous silence my suggestion  
has incited.


View raw message