Uploaded image for project: 'Lucene - Core'
  1. Lucene - Core
  2. LUCENE-1903

Incorrect ShingleFilter behavior when outputUnigrams == false

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.9
    • 2.9
    • modules/analysis
    • None
    • New

    Description

      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?

      Attachments

        1. TEST-org.apache.lucene.analysis.shingle.ShingleFilterTest.xml
          15 kB
          Chris Harris
        2. LUCENE-1903_testcases_lucene2_4_1_version.patch
          5 kB
          Chris Harris
        3. LUCENE-1903_testcases.patch
          5 kB
          Chris Harris
        4. LUCENE-1903.patch
          7 kB
          Uwe Schindler
        5. LUCENE-1903.patch
          8 kB
          Chris Harris

        Issue Links

          relates to

          Task - A task that needs to be done. LUCENE-1775 Change remaining contrib streams/filters to use new TokenStream API

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed

          Activity

            People

              uschindler Uwe Schindler
              ryguasu Chris Harris
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: