Re: MultiFieldQueryParser seems broken... Fix attached.

[sergiu gordea <gs...@ifit.uni-klu.ac.at>]

 Hi Bill,
 
  I think that more people wait for this patch of MultifieldIndexParser.
  It would be nice if it will be included in the next realease candidate 
....

    All the best,

   Sergiu

Bill Janssen wrote:

>René,
>
>Thanks for your note.
>
>I'd think that if a user specified a query "cutting lucene", with an
>implicit AND and the default fields "title" and "author", they'd
>expect to see a match in which both "cutting" and "lucene" appears.  That is,
>
>(title:cutting OR author:cutting) AND (title:lucene OR author:lucene)
>
>Instead, what they'd get using the current (broken) strategy of outer
>combination used by the current MultiFieldQueryParser, would be
>
>(title:cutting OR title:lucene) AND (author:cutting OR author:lucene)
>
>Note that this would match even if only "lucene" occurred in the
>document, as long as it occurred both in the title field and in the
>author field.  Or, for that matter, it would also match "Cutting on
>Cutting", by Doug Cutting :-).
>
>  
>
>>http://issues.apache.org/eyebrowse/ReadMsg?listName=lucene-user@jakarta.apache.org&msgId=1798116
>>    
>>
>
>Yes, the approach there is similar.  I attempted to complete the
>solution and provide a working replacement for MultiFieldQueryParser.
>
>Bill
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: lucene-user-help@jakarta.apache.org
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: lucene-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: lucene-user-help@jakarta.apache.org