Doug Cutting writes:
> >>http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1798116
> >
> >
> > Yes, the approach there is similar. I attempted to complete the
> > solution and provide a working replacement for MultiFieldQueryParser.
>
> But, inspired by that message, couldn't MultiFiel
Daniel Naber wrote:
On Thursday 09 September 2004 18:52, Doug Cutting wrote:
I have not been
able to construct a two-word query that returns a page without both
words in either the content, the title, the url or in a single anchor.
Can you?
Like this one?
konvens leitseite
Leitseite is only in
.
I reckon there has been a discussion (and solution :-) on how to achieve the
functionality you've been
after:
http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1798116
I'm not sure if this would be the same though.
Best regards,
René
Hi all,
I took the code indicated by Rene but I've
> But, inspired by that message, couldn't MultiFieldQueryParser just be a
> subclass of QueryParser that overrides getFieldQuery()?
I wasn't sure that everything "went through" getFieldQuery(). If so,
yes, that should work. In either case, I don't even think a subclass
is necessary. Just have
> is it a problem if the users will search "coffee OR tea" as a search
> string in the case that MultifieldQueryParser is
> modifyed as Bill suggested?, and the default opperator is set to AND?
>
Here's what you get (which is correct):
% java -classpath /usr/local/lib/lucene-1.4.1.jar:. \
On Thursday 09 September 2004 18:52, Doug Cutting wrote:
> I have not been
> able to construct a two-word query that returns a page without both
> words in either the content, the title, the url or in a single anchor.
> Can you?
Like this one?
konvens leitseite
Leitseite is only in the title o
Bill Janssen wrote:
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:lucen
René Hackl wrote:
is it a problem if the users will search "coffee OR tea" as a search
string in the case that MultifieldQueryParser is
modifyed as Bill suggested?, and the default opperator is set to AND?
No. There's not a problem with the proposed correction to MFQP. MFQP should
work the wa
> is it a problem if the users will search "coffee OR tea" as a search
> string in the case that MultifieldQueryParser is
> modifyed as Bill suggested?, and the default opperator is set to AND?
No. There's not a problem with the proposed correction to MFQP. MFQP should
work the way Bill suggested
René Hackl wrote:
Bill,
Thank you for clarifying on that issue. I missed the...
(title:cutting OR author:cutting) AND (title:lucene OR author:lucene)
...
(title:cutting OR title:lucene) AND (author:cutting OR author:lucene)
Note that this would match even if only "lucene" occurred in t
Bill,
Thank you for clarifying on that issue. I missed the...
> (title:cutting OR author:cutting) AND (title:lucene OR author:lucene)
...
> (title:cutting OR title:lucene) AND (author:cutting OR author:lucene)
>
> Note that this would match even if only "lucene" occurred in the
... "only luc
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
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 a
The class is at the end of the message.
But it hink that a better solution is that one suggested by Rene:
http://issues.apache.org/eyebrowse/[EMAIL PROTECTED]&msgId=1798116
Wermus Fernando wrote:
Bill,
I don't receive any .java. Could you send it again?
Thanks.
-Mensaje original-
Bill,
I don't receive any .java. Could you send it again?
Thanks.
-Mensaje original-
De: Bill Janssen [mailto:[EMAIL PROTECTED]
Enviado el: Martes, 07 de Septiembre de 2004 10:06 p.m.
Para: Lucene Users List
CC: Ali Rouhi
Asunto: MultiFieldQueryParser seems broken... Fix attached
Hi Bill,
-
But even if it didn't, the second
problem is that the query formed would be
+(title:cutting title:lucene) +(author:cutting author:lucene)
That is, if the word "Lucene" was in both the author field and the
title field, the match would fit. This clearly isn't what the
searcher i
16 matches
Mail list logo
