jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joel Richard (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-1312) Bundle nodes into a document
Date Thu, 24 Sep 2015 13:15:05 GMT

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

Joel Richard commented on OAK-1312:

One approach to decide which nodes should be saved together in a document could be to leverage
the node type and mixin information: If the type or mixins of a node allow or require certain
child nodes, then these child nodes would be stored together with the parent node in a single
document. Since a child node isn't read before it's parent anyway, nodes could still be retrieved
in the old way.

Example: Since a node with access control needs to have the rep:AccessControllable mixin and
the mixin suggests that a node with this mixin might have the rep:policy child node, these
two nodes would be stored together.

> Bundle nodes into a document
> ----------------------------
>                 Key: OAK-1312
>                 URL: https://issues.apache.org/jira/browse/OAK-1312
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core, mongomk
>            Reporter: Marcel Reutegger
> For very fine grained content with many nodes and only few properties per node it would
be more efficient to bundle multiple nodes into a single MongoDB document. Mostly reading
would benefit because there are less roundtrips to the backend. At the same time storage footprint
would be lower because metadata overhead is per document.

This message was sent by Atlassian JIRA

View raw message