lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yonik Seeley (JIRA)" <>
Subject [jira] [Commented] (SOLR-3998) Atomic update on uniqueKey field itself causes duplicate document
Date Fri, 26 Oct 2012 23:05:12 GMT


Yonik Seeley commented on SOLR-3998:

Thanks Eric - I've changed UpdateTest to include this scenario and replicated what you see.
I think the right thing to do here is probably throw an exception (rather than ignore the
modifiers on the id field).

> Atomic update on uniqueKey field itself causes duplicate document
> -----------------------------------------------------------------
>                 Key: SOLR-3998
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.0
>         Environment: Windows XP and RH Linux
>            Reporter: Eric Spencer
>            Assignee: Yonik Seeley
>         Attachments:
> 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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message