On Mar 3, 2005, at 1:32 PM, Doug Cutting wrote:
Daniel Naber wrote:
On Wednesday 02 March 2005 12:25, Erik Hatcher wrote:
I agree that the current behavior is awkward. Is it worth breaking
backwards compatibility to correct this with the patch applied?
I'd vote for fixing this as long as the curre
Daniel Naber wrote:
On Wednesday 02 March 2005 12:25, Erik Hatcher wrote:
I agree that the current behavior is awkward. Is it worth breaking
backwards compatibility to correct this with the patch applied?
I'd vote for fixing this as long as the current QueryParser is still available
in Lucene cor
> I agree that the current behavior is awkward. Is it worth breaking
> backwards compatibility to correct this with the patch applied?
IMHO, definitely.
The current behavior is so surprising that I doubt that no one is
relying on it.
I didn't really see this behavior explicitly pointed out in "
Omar Didi writes:
> I checked the code for the patch and I had no clue how to use it.
> can you please give me some instructions?
I guess it just patches QueryParser.jj so
patch < {patchfile}
in the directory where QueryParser.jj is found, should do (on the command
line of course).
If you're on
I checked the code for the patch and I had no clue how to use it.
can you please give me some instructions?
thanks
-Original Message-
From: Morus Walter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 02, 2005 9:01 AM
To: java-user@lucene.apache.org
Subject: RE: help with boolean
Omar Didi writes:
> thank you so much Eric and Morus, I have a clear idea now how it works. i
> will try to implement a custom code that adds the parenthesis to boolean
> expressions with some rules about operator precedence.
>
I rather suggest, that you patch QP instead.
Adding parenthesis be
: Wednesday, March 02, 2005 6:26 AM
To: Lucene Users List
Subject: Re: help with boolean expression
I'm deep into implementing a custom (not generalizable, sorry) query
parser and am evaluating this very issue now.
Lucene indeed does some funny stuff with boolean operators. Output the
toString of
On Wednesday 02 March 2005 12:25, Erik Hatcher wrote:
> I agree that the current behavior is awkward. Is it worth breaking
> backwards compatibility to correct this with the patch applied?
I'd vote for fixing this as long as the current QueryParser is still available
in Lucene core, maybe as Ol
To: Lucene Users List
Subject: Re: help with boolean expression
Omar Didi writes:
I have a problem understanding how would lucene iterpret this boolean
expression : A AND B OR C .
it neither return the same count as when I enter (A AND B) OR C nor A
AND (B OR C).
if anyone knows how it is interpret
