[
https://issues.apache.org/jira/browse/LUCENE-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553215
]
gsingers edited comment on LUCENE-25 at 12/18/07 7:27 PM:
-----------------------------------------------------------------
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.
In other words, I would like to close this.
was (Author: gsingers):
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
