You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2014/03/14 10:03:46 UTC

[jira] [Commented] (OAK-805) Support for existing Jackrabbit 2.x DataStores

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

Chetan Mehrotra commented on OAK-805:
-------------------------------------

Patch applied in revision http://svn.apache.org/r1577450

> Support for existing Jackrabbit 2.x DataStores
> ----------------------------------------------
>
>                 Key: OAK-805
>                 URL: https://issues.apache.org/jira/browse/OAK-805
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: core, mk, mongomk
>            Reporter: Jukka Zitting
>            Assignee: Chetan Mehrotra
>             Fix For: 0.19
>
>         Attachments: OAK-805.patch
>
>
> To speed up migrations from Jackrabbit 2.x to Oak and to allow multiple Oak repositories to share binaries like what's possible with the Jackrabbit 2.x DataStore mechanism, it would be good if our MKs, most notably MongoMK and SegmentMK, had a way to reference binaries stored in a DataStore instead of in the native blob store of the MK.
> The downside of such setups is of course that it splits up the garbage collection process, but the benefits of a speedier and less expensive migration will likely be worth it at least in some cases with huge amounts (TBs) of existing content.



--
This message was sent by Atlassian JIRA
(v6.2#6252)