You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by Oliver Hummel <hu...@informatik.uni-mannheim.de> on 2007/01/29 10:52:53 UTC

Potential feature request?

Hi,

I just stumbled across an issue with Lucene's QueryParser. Perhaps you already
discussed this here, but googling for it didn't bring me to a solution.

I realized that lucene is obviously not able to exclude fields, right? E.g.
something like

  -url:com

always delivers 0 results. Is this behaviour deliberate? Is there any rationale
for it?

Would it be possible to include such a feature, since it currently breaks the
use of the MultiFieldQueryParser as soon as a query with an exclude is entered.
Or would it at least be possible to modifiy the MFQP that applies excludes
somehow only for the content field?

Thanks in advance for any comments.

Best,

  Oliver


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


Re: Potential feature request?

Posted by Oliver Hummel <hu...@informatik.uni-mannheim.de>.
> I realized that lucene is obviously not able to exclude fields, right? E.g.
> something like
> 
>   -url:com
> 
> always delivers 0 results. Is this behaviour deliberate? Is there any rationale
> for it?

Ok, RTFM... :-)

http://lucene.apache.org/java/docs/queryparsersyntax.html
says that one exclude alone always delivers 0 results. Hm, I thought I tried it
with multiple terms, but obviously something went wrong. Everything seems to work.

Sorry, if I caused any confusion.

Best,

  Oliver





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