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 2017/05/04 08:40:04 UTC

[jira] [Commented] (OAK-6166) Support versioning in the federated node store

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

Chetan Mehrotra commented on OAK-6166:
--------------------------------------

[~tomek.rekawek] Last time when we discussed this then it was decided that as the private mount would be immutable there no actual use of version data from private mount. 

> Support versioning in the federated node store
> ----------------------------------------------
>
>                 Key: OAK-6166
>                 URL: https://issues.apache.org/jira/browse/OAK-6166
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: federated
>            Reporter: Tomek Rękawek
>             Fix For: 1.8
>
>
> The mount info provider should affect the versioning code as well, so version histories for the mounted paths are stored separately. Similarly to what we have in the indexing, let's store the mounted version histories under:
> /jcr:system/jcr:versionStorage/:oak:mount-MOUNTNAME



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)