[
https://issues.apache.org/jira/browse/OAK-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13511436#comment-13511436
]
Michael Dürig commented on OAK-464:
-----------------------------------
bq. Well, it would increase complexity of the MicroKernel implementations.
Please go back to
https://issues.apache.org/jira/browse/OAK-464?focusedCommentId=13511308&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13511308
and read.
That particular functionality *is already there* in the Microkernel. Making it
more explicit will by no means increase complexity but rather to the contrary.
It will help clarifying a rather obscure part of the current Microkernel
implementation: namely how conflicts are handled.
BTW, this is something I criticised over a ago year already [1] and which was
subsequently extenuated [2].
[1]
http://wiki.apache.org/jackrabbit/Transactional%20model%20of%20the%20Microkernel%20based%20Jackrabbit%20prototype?action=recall&rev=1
[2]
http://wiki.apache.org/jackrabbit/Transactional%20model%20of%20the%20Microkernel%20based%20Jackrabbit%20prototype?action=diff&rev1=2&rev2=3
> 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
