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

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 4.0-BETA, 6.0
    • None
    • 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

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

          People

            hossman Chris M. Hostetter
            hossman Chris M. Hostetter
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment