You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2013/11/06 21:10:19 UTC

[jira] [Resolved] (OAK-1036) SegmentMK: Auto-flushing SegmentNodeBuilder

     [ https://issues.apache.org/jira/browse/OAK-1036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting resolved OAK-1036.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 0.11
         Assignee: Jukka Zitting

This works pretty well now.

> SegmentMK: Auto-flushing SegmentNodeBuilder
> -------------------------------------------
>
>                 Key: OAK-1036
>                 URL: https://issues.apache.org/jira/browse/OAK-1036
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: core
>            Reporter: Jukka Zitting
>            Assignee: Jukka Zitting
>            Priority: Minor
>             Fix For: 0.11
>
>
> It would be good if the {{NodeBuilder}} mechanism could be more tightly integrated with the SegmentMK internals through the {{SegmentNodeBuilder}} class. The primary benefit of this would be to implement the auto-flushing functionality enabled by OAK-659.
> Additionally, it should for example be possible to automatically write-ahead parts of transient change set to segments or to make the {{getNodeState()}} call always return {{SegmentNodeState}} s instead of having to repeatedly use the {{MutableNodeState.snapshot()}} mechanism that's currently dragging performance in some of our benchmarks (most notably XML imports).



--
This message was sent by Atlassian JIRA
(v6.1#6144)