[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=16240118#comment-16240118 ] Tomek Rękawek commented on OAK-6166: [~rombert] - sure, done. > 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: composite >Reporter: Tomek Rękawek >Priority: Minor > Fix For: 1.9.0 > > > 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.4.14#64029)
[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=16240088#comment-16240088 ] Robert Munteanu commented on OAK-6166: -- [~tomek.rekawek] - should we postpone this for a later version? > 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: composite >Reporter: Tomek Rękawek >Priority: Minor > 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.4.14#64029)
[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=15997965#comment-15997965 ] Chetan Mehrotra commented on OAK-6166: -- Yes for sharding this feature would indeed be required and the approach we have used so far for property index can be used here also i.e. create mount specific root nodes under which versions are created > 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 >Priority: Minor > 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)
[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=15997872#comment-15997872 ] Tomek Rękawek commented on OAK-6166: [~chetanm], that's true for the current application of the federated node store (blue-green deployments, etc.). However in the future the federated node store can be also used for other purposes (eg. content-aware sharding) and then it may be helpful to support all the Oak features, including this one. I may lower the priority to minor for now. WDYT? > 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)
[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=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)
