Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Message-ID: <796994515.1249481715087.JavaMail.jira@brutus>
Date: Wed, 5 Aug 2009 07:15:15 -0700 (PDT)
From: "Stefan Guggisberg (JIRA)" <jira@apache.org>
To: dev@jackrabbit.apache.org
Subject: [jira] Commented: (JCR-642) Support flat content hierarchies
In-Reply-To: <16816858.1164096481964.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/JCR-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739517#action_12739517 ] 

Stefan Guggisberg commented on JCR-642:
---------------------------------------

@lars:

i am less enthousiastic about thomas' proposal. please keep in mind that a lot of code all over jackrabbit's core would probably need to be touched, with a high risk of introducing new bugs. personally i doubt that the 'feature' is worth taking this risk...

if we decide that very flat hierarchies is a use case we want to support, then this should be taken into account when redesigning jackrabbit's core from scratch.

> 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.