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

schema should fail hard if uniqueKey field is multivalued

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

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0-BETA, 6.0
    • Component/s: None
    • Labels:
      None

      Description

      Solr 3.1 stated logging a SEVERE warning if uniqueKeyField field was used, but was multiValued. This was done only as a log message so users who upgraded and had old configs where the field was multiValued (or inherited the multiValueness from the fieldtype) would continue to work, as long as they used the field properly.

      But this is still causing some confusion...

      http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201207.mbox/%3CCAN4YXvcjr5Vh9LHYUi3PeJZwDgBpd9EZ5fyWBAgHCWQ+tPsFwg@mail.gmail.com%3E

      ...for 4.0, we should hard fail if uniqueKeyField is used nad doesn't mean the neccessary requirements to function properly.

        Attachments

        Issue Links

          Activity

            People

            • Assignee:
              hossman Chris M. Hostetter
              Reporter:
              hossman Chris M. Hostetter

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment