jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-642) Support flat content hierarchies
Date Tue, 21 Nov 2006 08:08:01 GMT
Support flat content hierarchies
--------------------------------

                 Key: JCR-642
                 URL: http://issues.apache.org/jira/browse/JCR-642
             Project: Jackrabbit
          Issue Type: Improvement
          Components: 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message