You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/02/01 18:30:39 UTC
[jira] [Updated] (OAK-3937) Batch createOrUpdate() may fail with
primary key violation
[ https://issues.apache.org/jira/browse/OAK-3937?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Reschke updated OAK-3937:
--------------------------------
Attachment: OAK-3937.diff
work in progress; with printlns added to code and test case; it seems the failure (*) has to do with the retry logic, but so far I don't see what exactly goes wrong.
(*) as observed by the test: we don't have an "old" document for each of the ones we created/updated.
> Batch createOrUpdate() may fail with primary key violation
> ----------------------------------------------------------
>
> Key: OAK-3937
> URL: https://issues.apache.org/jira/browse/OAK-3937
> Project: Jackrabbit Oak
> Issue Type: Technical task
> Components: core, rdbmk
> Reporter: Marcel Reutegger
> Assignee: Julian Reschke
> Fix For: 1.4
>
> Attachments: OAK-3937.diff, OAK-3937.patch, rdb-oddity.patch
>
>
> In some cases the batch createOrUpdate() method may fail on RDBMK with a primary key violation exception.
> {noformat}
> java.lang.AssertionError: org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: org.h2.jdbc.JdbcBatchUpdateException: Unique index or primary key violation: "PRIMARY_KEY_1 ON PUBLIC.DSTEST_NODES(ID) VALUES ('1:/node-40', 118)"; SQL statement:
> insert into dstest_NODES(ID, MODIFIED, HASBINARY, DELETEDONCE, MODCOUNT, CMODCOUNT, DSIZE, DATA, BDATA) values (?, ?, ?, ?, ?, ?, ?, ?, ?) [23505-185]
> {noformat}
> See the currently disabled test {{MultiDocumentStoreTest.concurrentBatchUpdate()}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)