[
https://issues.apache.org/jira/browse/OAK-633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583015#comment-13583015
]
Jukka Zitting commented on OAK-633:
-----------------------------------
Initial work in revision 1448545.
An interesting question came up when thinking about this: Should commit hooks
be executed during the cross-journal merges? This cold be implemented by having
the journals keep separate track of the changes made by the client and the
commit hooks. Then during the journal merge only changes that originated from
the client would be rebased and the commit hooks re-executed on the resulting
larger merge commit before updating the root journal.
The benefit of this approach would be that commit hooks which update shared
data structures like in-content indexes wouldn't have to worry about the
effects of an automated merge of the updates done by two or more concurrently
running hooks. The downside is that it further complicates merge processing and
might cause the journal merge to be rejected due to some validation error.
> SegmentMK: Hierarchy of journals
> --------------------------------
>
> Key: OAK-633
> URL: https://issues.apache.org/jira/browse/OAK-633
> Project: Jackrabbit Oak
> Issue Type: Sub-task
> Components: segmentmk
> Reporter: Jukka Zitting
>
> The current SegmentMK draft implementation only supports a single root
> journal, and thus still has the same concurrent write bottleneck as the other
> MK implementations. To avoid this bottleneck we should implement support for
> multiple, hierarchically organized journals as outlined in the proposed
> SegmentMK design.
--
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
