Lucene - Core
  1. Lucene - Core
  2. LUCENE-3301

add workaround for jre breakiterator bugs

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.5, 4.0-ALPHA
    • Component/s: None
    • Labels:
      None
    • Lucene Fields:
      New

      Description

      on some inputs, the java breakiterator support will internally crash.

      for example: ant test -Dtestcase=TestThaiAnalyzer -Dtestmethod=testRandomStrings -Dtests.seed=-8005471002120855329:-2517344653287596566 -Dtests.multiplier=3

        Activity

        Hide
        Robert Muir added a comment -

        attached is a patch with workarounds

        Show
        Robert Muir added a comment - attached is a patch with workarounds
        Hide
        Michael McCandless added a comment -

        Charlie just hit this. Patch looks good to me!

        Show
        Michael McCandless added a comment - Charlie just hit this. Patch looks good to me!
        Show
        Robert Muir added a comment - http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7104012
        Hide
        DM Smith added a comment -

        Robert, do you know why the bug you provided the link does not find anything?

        Show
        DM Smith added a comment - Robert, do you know why the bug you provided the link does not find anything?
        Hide
        Robert Muir added a comment -

        I just submitted the bug report this morning. I think it takes a while (days, weeks) to become visible... worst bug tracker EVER!

        Show
        Robert Muir added a comment - I just submitted the bug report this morning. I think it takes a while (days, weeks) to become visible... worst bug tracker EVER!
        Hide
        Dawid Weiss added a comment -

        I think what happens is all bugs are initially internal to Oracle and they need to be "opened up" to the public. I presume this is so that critical bug reports don't immediately become available for exploits... but I'm just guessing.

        Show
        Dawid Weiss added a comment - I think what happens is all bugs are initially internal to Oracle and they need to be "opened up" to the public. I presume this is so that critical bug reports don't immediately become available for exploits... but I'm just guessing.
        Hide
        Uwe Schindler added a comment -

        Bulk close after release of 3.5

        Show
        Uwe Schindler added a comment - Bulk close after release of 3.5

          People

          • Assignee:
            Robert Muir
            Reporter:
            Robert Muir
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development