On Monday 15 November 2004 20:00, Christiaan Fluit wrote: > I'm not sure whether we are thinking alike here. Judging from the code > in 1.4.2, I expect the query "X AND Y" to be evaluated as: > > (field1:X AND field1:Y) OR (field2:X AND field2:Y) OR ... (fieldn:X AND > fieldn:Y)
Yes, that's the way Lucene currently behaves. > is somewhat counter-intuitive. When I enter this query, I would except > it to be evaluated as: > > (field1:X OR field2:X OR ... fieldn:X) AND (field1:Y OR field2:Y OR ... > fieldn:Y) That's what the new implementation will return. For OR queries it shouldn't make a difference, so the new implementation can replace the old one. Regards Daniel -- http://www.danielnaber.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
