[
https://issues.apache.org/jira/browse/SOLR-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13485069#comment-13485069
]
Eric Spencer commented on SOLR-3998:
------------------------------------
Obviously, the workaround is to make sure that you don't do an atomic update on
the uniqueKey field itself (which I was sort of doing by accident anyway). I
just don't think anything should allow the violating of the uniqueKey.
> Atomic update on uniqueKey field itself causes duplicate document
> -----------------------------------------------------------------
>
> Key: SOLR-3998
> URL: https://issues.apache.org/jira/browse/SOLR-3998
> Project: Solr
> Issue Type: Bug
> Affects Versions: 4.0
> Environment: Windows XP and RH Linux
> Reporter: Eric Spencer
> Attachments: solr_atomic_update_unique_key_bug_t.java
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
