[
https://issues.apache.org/jira/browse/LUCENE-1903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752838#action_12752838
]
Chris Harris commented on LUCENE-1903:
--------------------------------------
bq. Chris: Could you test this patch
Looks ok so far, but unfortunately I doubt I'll be able to test it in a
real-world setting before you guys want to freeze the code and/or release. (I
usually use not just ShingleFilter but ShingleFilter combined with the
LUCENE-1370 patch. It was in looking into to upgrading LUCENE-1370 to work with
the trunk that I discovered this bug.)
> 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
> Affects Versions: 2.9
> Reporter: Chris Harris
> Fix For: 2.9
>
> Attachments: LUCENE-1903.patch, LUCENE-1903.patch,
> LUCENE-1903_testcases.patch, LUCENE-1903_testcases_lucene2_4_1_version.patch,
> TEST-org.apache.lucene.analysis.shingle.ShingleFilterTest.xml
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
