[
https://issues.apache.org/jira/browse/OAK-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526266#comment-13526266
]
Michael Dürig commented on OAK-464:
-----------------------------------
bq. As I already wrote, why doesn't oak-core keep track of the list of
operations?
This is a architectural decision which was discussed at length, and which you
should be aware of. I initially wasn't in favour of this decision neither but
the consensus was otherwise and I suggest we stick with it.
bq. As I already wrote, implementing it once in oak-core is not duplicating
code.
See [Jukka's comment
above|https://issues.apache.org/jira/browse/OAK-464?focusedCommentId=13526207&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13526207].
It is not sufficient to have it in oak-core alone. Any Microkernel
implementation will have to cope with this anyway.
> 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
