jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Dürig (JIRA) <j...@apache.org>
Subject [jira] [Commented] (OAK-106) Use NodeStateBuilder instances to record changes in TreeImpl
Date Mon, 21 May 2012 17:42:40 GMT

    [ https://issues.apache.org/jira/browse/OAK-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13280302#comment-13280302

Michael Dürig commented on OAK-106:

Revision 1341123 is an initial implementation of this. Properly reverting changes on refresh
and save is still missing. See TODOs in {{TreeImpl.revert()}} and {{TreeImpl.saved()}}.
> Use NodeStateBuilder instances to record changes in TreeImpl
> ------------------------------------------------------------
>                 Key: OAK-106
>                 URL: https://issues.apache.org/jira/browse/OAK-106
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
> Since OAK-102 NodeStore exposes the branch feature. The initial implementation of TreeImpl
on top of this eagerly writes all changes down to the NodeStoreBranch by acquiring a new NodeStateBuilder
based on the current NodeState for each change. A better implementation would instead use
a NodeStateBuilder per TreeImpl to accumulated the changes and only purge them down to the
branch when necessary.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message