[
https://issues.apache.org/jira/browse/OAK-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14298399#comment-14298399
]
Stefan Thieme commented on OAK-1914:
------------------------------------
Yes, I believe it is store.create(NODES, newNodes) that tries to commit/create
the root node ("1:/test" in my case) again.
org.apache.jackrabbit.oak.plugins.document.Commit.applyToDocumentStore
...
try {
if (newNodes.size() > 0) {
// set commit root on new nodes
if (!store.create(NODES, newNodes)) {
// some of the documents already exist:
// try to apply all changes one by one
for (UpdateOp op : newNodes) {
if (op == commitRoot) {
...
Does this mean that the ORA-00001 Constraint violation should be ignored /
could be handled more gracefully as the newNodes are updated anyway ?
> RDB: Oracle support
> -------------------
>
> Key: OAK-1914
> URL: https://issues.apache.org/jira/browse/OAK-1914
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: rdbmk
> Reporter: Julian Reschke
> Assignee: Julian Reschke
> Priority: Minor
> Fix For: 1.2
>
> Attachments: OAK-1914.patch, insert2.log, oak_20150127.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
