[
https://issues.apache.org/jira/browse/OAK-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13533729#comment-13533729
]
Thomas Mueller commented on OAK-464:
------------------------------------
> doubling the traffic going through the Microkernel API
I thought reading the journal is only required if oak-core created a branch
that the MicroKernel couldn't merge due to a conflict?
> roughly doubling the memory requirements of sessions because they need to fit
> the journal into memory
As far as I know, this will not actually increase the memory requirement
compared to implementing it in the MicroKernel, because the MicroKernel would
need to do basically the same.
> increased probability of conflicts compared to the previous approach
> for example - a session does ^/foo:42 ^/foo:null
What would be the JCR API method calls needed that would cause a session to do
that?
> after a conflict, resolution becomes impossible from within the conflicting
> session
Isn't the JCR method supposed to fail if there is/was a conflicting update? If
not, what conflicts is oak-core supposed to resolve automatically?
> 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
