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 "Michael Dürig (JIRA)" <ji...@apache.org> on 2013/09/24 12:05:03 UTC
[jira] [Updated] (OAK-1036) SegmentMK: Auto-flushing SegmentNodeBuilder

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

Michael Dürig updated OAK-1036:
-------------------------------

    Description: 
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).

  was:
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).

    
> 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
>            Priority: Minor
>
> 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 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