You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Grant Ingersoll (JIRA)" <ji...@apache.org> on 2007/12/19 04:17:43 UTC

[jira] Updated: (LUCENE-25) QueryParser produces empty BooleanQueries when all clauses are stop words

     [ https://issues.apache.org/jira/browse/LUCENE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Grant Ingersoll updated LUCENE-25:
----------------------------------

    Attachment: LUCENE-25.patch

Attached patch adds a test to QP for this.  It now seems like QP is doing reasonable things with stopwords at least for a few cases.   Of course, I am not sure what QP should return when all the terms are stopwords (it currently returns a BooleanQuery with zero clauses)

I am not sure when this was fixed.

> QueryParser produces empty BooleanQueries when all clauses are stop words
> -------------------------------------------------------------------------
>
>                 Key: LUCENE-25
>                 URL: https://issues.apache.org/jira/browse/LUCENE-25
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: QueryParser
>    Affects Versions: 1.0.2
>         Environment: Operating System: All
> Platform: PC
>            Reporter: Puk Witte
>         Attachments: LUCENE-25.patch, patch9.txt
>
>
> When I want to do the following query (example):
> (fieldx : xxxxx OR fieldy : xxxxxxxx)AND(fieldx : stopword OR fieldy : stopword)
> it will search (after passing the Analyzer including a StopFilter) for 
> (fieldx : xxxxx OR fieldy : xxxxxx) AND() and give a wrong searchresult or a 
> NullPointerException.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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