[
https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12792389#action_12792389
]
Stefan Guggisberg commented on JCR-642:
---------------------------------------
> Is this issue still under consideration?
yes
> It's a big issue for our organization, and we are considering whether we need
> to build a workaround for it or wait for resolution in Jackrabbit itself.
support for flat hierarchies is IMO one of the design goals of a complete
redesign/rewrite of the jackrabbit core (i.e. version 3.0).
so i wouldn't hold my breath for jackrabbit supporting it within the next
couple of months...
> Support flat content hierarchies
> --------------------------------
>
> Key: JCR-642
> URL: https://issues.apache.org/jira/browse/JCR-642
> Project: Jackrabbit Content Repository
> Issue Type: Improvement
> Components: jackrabbit-core
> Reporter: Jukka Zitting
>
> The current best practice with Jackrabbit is to avoid flat content structures
> due to performance concerns.
> These concerns are caused by the fact that the NodeState implementation
> requires the list of child node names and identifiers to be available at all
> times. In fact many (all?) current persistence managers implement this
> requirement by storing and loading this list as a part of the serialized node
> state. When this list grows, the performance and memory overhead of managing
> the list grows as well. As a side note, this also creates potential
> consistency issues since the parent/child links are stored both within the
> child list of the parent node and as the parent link of the child node.
> To solve this issue, I believe we need to break the tight bonding between the
> node state and the list of child nodes. This will likely require major
> refactoring of the Jackrabbit core, including breaking the NodeState and
> PersistenceManager interfaces, so I don't expect a solution in near future.
> However, we should start thinking about how to best do this, and at least be
> concerned about building in any more assumptions about the list of child
> nodes always being readily available.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
