[jira] [Commented] (SOLR-3998) Atomic update on uniqueKey field itself causes duplicate document

["Commit Tag Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13610628#comment-13610628 ] 

Commit Tag Bot commented on SOLR-3998:
--------------------------------------

[branch_4x commit] Yonik Seeley
http://svn.apache.org/viewvc?view=revision&revision=1402743

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

                
> 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
>            Assignee: Yonik Seeley
>             Fix For: 4.1
>
>         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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org