lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Harris (JIRA)" <j...@apache.org>
Subject [jira] Created: (LUCENE-1903) Incorrect ShingleFilter behavior when outputUnigrams == false
Date Tue, 08 Sep 2009 20:55:57 GMT
Incorrect ShingleFilter behavior when outputUnigrams == false
-------------------------------------------------------------

                 Key: LUCENE-1903
                 URL: https://issues.apache.org/jira/browse/LUCENE-1903
             Project: Lucene - Java
          Issue Type: Bug
          Components: contrib/analyzers
            Reporter: Chris Harris


ShingleFilter isn't working as expected when outputUnigrams == false. In particular, it is
outputting unigrams at least some of the time when outputUnigrams==false.

I'll attach a patch to ShingleFilterTest.java that adds some test cases that demonstrate the
problem.

I haven't checked this, but I hypothesize that the behavior for outputUnigrams == false got
changed when the class was upgraded to the new TokenStream API?

-- 
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


Mime
View raw message