Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

      When WordDelimiterFilter is set to generate*Parts=0 and catenate*Parts=0 (for either Number or Word), it throws an exception when encountering such a token in the token stream. This might be uncommon, but it should be possible (for instance, to filter out all numbers).

        Activity

        Hide
        Mike Klaas added a comment -

        TestCase demonstrating the issue and patch to WordDelimiterFilter which corrects it.

        Resolution: if catenate and generate are off, the filter skips to the next token instead of throwing an exception.

        Show
        Mike Klaas added a comment - TestCase demonstrating the issue and patch to WordDelimiterFilter which corrects it. Resolution: if catenate and generate are off, the filter skips to the next token instead of throwing an exception.
        Hide
        Yonik Seeley added a comment -

        Committed. Thanks Mike!
        I patched the test by hand (the patch failed). I think this was because the svn:eol-style native property wasn't set to prevent newline changes from messing everything up.

        Show
        Yonik Seeley added a comment - Committed. Thanks Mike! I patched the test by hand (the patch failed). I think this was because the svn:eol-style native property wasn't set to prevent newline changes from messing everything up.
        Hide
        Hoss Man added a comment -

        This bug was modified as part of a bulk update using the criteria...

        • Marked ("Resolved" or "Closed") and "Fixed"
        • Had no "Fix Version" versions
        • Was listed in the CHANGES.txt for 1.1

        The Fix Version for all 38 issues found was set to 1.1, email notification
        was suppressed to prevent excessive email.

        For a list of all the issues modified, search jira comments for this
        (hopefully) unique string: 20080415hossman3

        Show
        Hoss Man added a comment - This bug was modified as part of a bulk update using the criteria... Marked ("Resolved" or "Closed") and "Fixed" Had no "Fix Version" versions Was listed in the CHANGES.txt for 1.1 The Fix Version for all 38 issues found was set to 1.1, email notification was suppressed to prevent excessive email. For a list of all the issues modified, search jira comments for this (hopefully) unique string: 20080415hossman3

          People

          • Assignee:
            Yonik Seeley
            Reporter:
            Mike Klaas
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development