lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Spencer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SOLR-3998) Atomic update on uniqueKey field itself causes duplicate document
Date Fri, 26 Oct 2012 17:45:14 GMT

     [ https://issues.apache.org/jira/browse/SOLR-3998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Eric Spencer updated SOLR-3998:
-------------------------------

    Attachment: solr_atomic_update_unique_key_bug_t.java

JUnit 4 test case demonstrating the problem.
                
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message