[SOLR-3998] Atomic update on uniqueKey field itself causes duplicate document

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.0
• Fix Version/s: 4.1

Environment

Windows XP and RH Linux

• Assignee: Yonik Seeley
• Reporter: Eric Spencer
• Created: 26/Oct/12 17:40
• Updated: 22/Mar/13 16:22
• Resolved: 27/Oct/12 05:53

Description

Issuing an atomic update which includes the uniqueKey field itself will cause Solr to insert a second document with the same uniqueKey thereby violating uniqueness. A non-atomic update will "correct" the document. Attached is a JUnit test case that demonstrates the issue against the collection1 core in the standard Solr download.