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

Back-compat break with non-ascii field names

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.4, 2.4.1
    • 2.9
    • core/index
    • None
    • New

    Description

      If a field name contains non-ascii characters in a 2.3.x index, then
      on upgrade to 2.4.x unexpected problems are hit. It's possible to hit
      a "read past EOF" IOException; it's also possible to not hit an
      exception but get an incorrect field name.

      This was caused by LUCENE-510, because the FieldInfos (*.fnm) file is
      not properly versioned.

      Spinoff from http://www.nabble.com/Read-past-EOF-td23276171.html

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            mikemccand Michael McCandless
            mikemccand Michael McCandless
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment