Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-3226

SignatureUpdateProcessor ignores non-string field values from the signature generation

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

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.4, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0-ALPHA
    • 3.6, 4.0-ALPHA
    • update
    • None

    Description

      When using for example XMLUpdateRequestProcessor, the signature is calculated correctly since all field values are strings. But when one uses DataImportHandler or BinaryUpdateRequestHandler, the signature generation will ignore any field values that are ints, longs, dates etc.

      This might result in overwriting non-similar documents, as it happened in my case while importing some db data through DIH.

      Attachments

        1. SOLR-3226.patch
          5 kB
          Spyros Kapnissis
        2. SOLR-3226.patch
          7 kB
          Chris M. Hostetter

        Issue Links

        is related to

        Bug - A problem which impairs or prevents the functions of the product. SOLR-3200 When using SignatureUpdateProcessor with "all fields" configuration, it will assume only the fields present on the very first document only, ignoring any optional fields in subsequent documents in the signature generation.

        • Major - Major loss of function.
        • Closed

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

          People

            hossman Chris M. Hostetter
            spyk Spyros Kapnissis
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment