[
https://issues.apache.org/jira/browse/OAK-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663922#comment-13663922
]
Jukka Zitting commented on OAK-834:
-----------------------------------
bq. I think if it would have been an option to kept all data in one repository,
then we wouldn't end up with JCR-3534 / OAK-834.
Right. The way I see it, the architectural limitations of Jackrabbit play a big
part in why that solution hasn't been a viable option so far. In Oak without
those limitations the situation is different, so I'd be surprised if someone
who starts from a clean slate with Oak would come up with a requirement like
this.
Anyway, given existing deployments and backwards compatibility requirements, it
seems clear that we in any case need to do something in this area. The
suggested support for existing Jackrabbit DataStores should be a good starting
point.
> Efficient copying of binaries across repositories with the same MK
> ------------------------------------------------------------------
>
> Key: OAK-834
> URL: https://issues.apache.org/jira/browse/OAK-834
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: mk
> Reporter: Tommaso Teofili
>
> As a follow up on JCR-3534 discussions and implementation, we should also
> discuss how to handle a similar scenario in Oak.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
