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/04 21:26:17 UTC

[jira] [Resolved] (OAK-210) granularity of persisted data

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

Jukka Zitting resolved OAK-210.
-------------------------------

    Resolution: Incomplete

Resolving as Incomplete without more specific description of what/where needs to be done. So far the SegmentMK already addresses this by grouping related content into larger segments.

> granularity of persisted data
> -----------------------------
>
>                 Key: OAK-210
>                 URL: https://issues.apache.org/jira/browse/OAK-210
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mk
>            Reporter: Stefan Guggisberg
>            Assignee: Stefan Guggisberg
>
> the current persistence granularity is _single nodes_ (a node consists of properties and child node information). 
> instead of storing/retrieving single nodes it would IMO make sense to store subtree aggregates of specific nodes. the choice of granularity could be based on simple filter criteria (e.g. property value).
> dynamic persistence granularity would help reducing the number of records and r/w operations on the underlying store, thus improving performance.  



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