jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Guggisberg (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-210) granularity of persisted data
Date Fri, 27 Jul 2012 13:30:35 GMT

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

Stefan Guggisberg commented on OAK-210:

bq. Do you see this as something to be implemented (or not) by each MK independently (i.e.
something like an MK implementation detail)?

no, that's an implementation detail that doesn't affect the semantics of the MicroKernel API.

the most notable impact will be that the current implementation won't be able to provide {{:hash}}
values for _every_ node. but that's already explicitly allowed for, see {{Microkernel#getNodes}}
java doc.
> granularity of persisted data
> -----------------------------
>                 Key: OAK-210
>                 URL: https://issues.apache.org/jira/browse/OAK-210
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          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 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