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

Non-tokenized fields become tokenized when a document is deleted and added back

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

Details

    • Bug
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 4.0-ALPHA
    • None
    • core/index
    • None
    • New

    Description

      https://github.com/bimargulies/lucene-4-update-case is a JUnit test case that seems to show a problem with the current trunk. It creates a document with a Field typed as StringField.TYPE_STORED and a value with a "-" in it. A TermQuery can find the value, initially, since the field is not tokenized.

      Then, the case reads the Document back out through a reader. In the copy of the Document that gets read out, the Field now has the tokenized bit turned on.

      Next, the case deletes and adds the Document. The 'tokenized' bit is respected, so now the field gets tokenized, and the result is that the query on the term with the - in it no longer works.

      So I think that the defect here is in the code that reconstructs the Document when read from the index, and which turns on the tokenized bit.

      I have an ICLA on file so you can take this code from github, but if you prefer I can also attach it here.

      Attachments

        Activity

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

          People

            Unassigned Unassigned
            bmargulies Benson Margulies

            Dates

              Created:
              Updated:

              Slack

                Issue deployment