You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Muir (JIRA)" <ji...@apache.org> on 2010/01/10 12:14:54 UTC
[jira] Commented: (LUCENE-2202) PhraseQuery will not find hits
containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is
used
[ https://issues.apache.org/jira/browse/LUCENE-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12798464#action_12798464 ]
Robert Muir commented on LUCENE-2202:
-------------------------------------
Hello Philipp,
the tokenize() method in this testcase has a bug, it completely ignores the position increments from the tokenstream.
this is what is causing your problem.
> PhraseQuery will not find hits containing stop words when StandardAnalyzer with 2.9 or 3.0 semantics is used
> ------------------------------------------------------------------------------------------------------------
>
> Key: LUCENE-2202
> URL: https://issues.apache.org/jira/browse/LUCENE-2202
> Project: Lucene - Java
> Issue Type: Bug
> Components: Analysis
> Affects Versions: 3.0
> Environment: JRE6
> Reporter: Philipp Nanz
> Attachments: TestCase.java
>
>
> When you add a document with an analyzed field containing a stopword to the index using standardanalyzer, the behaviour will be inconsistent depending on which version semantics where used with StandardAnalyzer.
> Using 2.4 semantics the document can subsequently be found using PhraseQuery. Using the very same test with 2.9 or 3.0 semantics will fail.
--
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