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

Michael Dürig commented on JCR-3311:
------------------------------------

Not sure about the 2.13 part, however upgrading from Jackrabbit 2 to Oak is 
supported through the upgrade run mode of {{oak-run}}. See 
https://github.com/apache/jackrabbit-oak/blob/trunk/oak-run/README.md

> 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.2, 2.3, 2.4
>            Reporter: David Hausladen
>            Assignee: Michael Dürig
>            Priority: Minor
>              Labels: flat, repository
>         Attachments: NodeWrapper.java
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to