[
https://issues.apache.org/jira/browse/OAK-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508674#comment-13508674
]
Thomas Mueller commented on OAK-464:
------------------------------------
> The loss of custom conflict handling logic is unfortunate
I think conflict resolution needs to handled in oak-core. I'm worried that it
is not possible to (correctly) solve all possible conflicts within the
MicroKernel.
> Implement the rebase operation on top of the Microkernel (status quo)
> -0 For the performance and complexity overhead.
To me it sounds like you want to avoid complexity in oak-core and therefore
request to implement it in the MicroKernel. To me it sounds like the wrong
thing to do.
> Is each of those commits atomic?
> Yes, though since they're against a branch, there's no need to worry about
> concurrent commits.
My question was, what should the MicroKernel do if one of the commit fails
because of a conflict. My question wasn't about concurrency.
> RootImpl.rebase() doesn't handle move operations correctly
> ----------------------------------------------------------
>
> Key: OAK-464
> URL: https://issues.apache.org/jira/browse/OAK-464
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Michael Dürig
>
> Doing {{RootImpl.rebase()}} causes moves to be changed to remove followed by
> add. Which causes moves of large sub trees to become very expensive.
--
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
