David Hausladen created JCR-3311:
------------------------------------
Summary: No mechanism to transparently engage BTreeManager for
flat repositories
Key: JCR-3311
URL: https://issues.apache.org/jira/browse/JCR-3311
Project: Jackrabbit Content Repository
Issue Type: Bug
Components: jackrabbit-jcr-commons
Affects Versions: 2.4, 2.3, 2.2
Reporter: David Hausladen
For someone to enjoy the benefits of the BTreeManager to map between an
external, flat path and an internally-branching tree, he must use
jackrabbit-specific classes to achieve it. This is is undesirable. It would
be better if, through configuration, he could specify that his paths are likely
flat and Jackrabbit would return implementations of the Node interface that
would interact with the BTreeManager internally so that the application code
could remain agnostic of the internal challenges of dealing with large numbers
of child nodes.
I've attached NodeWrapper.java which is a preliminary attempt at adapting the
Node interface to the BTreeManager. In practice, however, I found that if the
returned, wrapped Nodes were interrogated for their path, they would return the
internal, rather than external, paths. Without an approach to address this
problem, I abandoned testing.
I would not have a problem with an assumption that the configuration option
must be chosen at repository creation time and must not be changed thereafter.
--
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
