[jira] [Updated] (OAK-3131) DocumentNodeStore doesn't serialize blobs that have been created in a different store
[ https://issues.apache.org/jira/browse/OAK-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-3131: --- Fix Version/s: 1.0.33 > DocumentNodeStore doesn't serialize blobs that have been created in a > different store > - > > Key: OAK-3131 > URL: https://issues.apache.org/jira/browse/OAK-3131 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, upgrade >Affects Versions: 1.2.2, 1.3.2, 1.0.17 >Reporter: Manfred Baedke >Assignee: Manfred Baedke > Fix For: 1.4, 1.3.3, 1.2.17, 1.0.33 > > > During a RepositorySidegrade migration it may happen that DocumentNodeStore > has to write a blob that has been created in another instance, but fails > because it has been optimized for the usual scenario where there is just one > instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3131) DocumentNodeStore doesn't serialize blobs that have been created in a different store
[ https://issues.apache.org/jira/browse/OAK-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomek Rękawek updated OAK-3131: --- Fix Version/s: 1.2.17 > DocumentNodeStore doesn't serialize blobs that have been created in a > different store > - > > Key: OAK-3131 > URL: https://issues.apache.org/jira/browse/OAK-3131 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, upgrade >Affects Versions: 1.2.2, 1.3.2, 1.0.17 >Reporter: Manfred Baedke >Assignee: Manfred Baedke > Fix For: 1.4, 1.3.3, 1.2.17 > > > During a RepositorySidegrade migration it may happen that DocumentNodeStore > has to write a blob that has been created in another instance, but fails > because it has been optimized for the usual scenario where there is just one > instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3131) DocumentNodeStore doesn't serialize blobs that have been created in a different store
[ https://issues.apache.org/jira/browse/OAK-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-3131: Fix Version/s: 1.3.3 > DocumentNodeStore doesn't serialize blobs that have been created in a > different store > - > > Key: OAK-3131 > URL: https://issues.apache.org/jira/browse/OAK-3131 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, upgrade >Affects Versions: 1.2.2, 1.3.2, 1.0.17 >Reporter: Manfred Baedke >Assignee: Manfred Baedke > Fix For: 1.3.3 > > > During a RepositorySidegrade migration it may happen that DocumentNodeStore > has to write a blob that has been created in another instance, but fails > because it has been optimized for the usual scenario where there is just one > instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3131) DocumentNodeStore doesn't serialize blobs that have been created in a different store
[ https://issues.apache.org/jira/browse/OAK-3131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manfred Baedke updated OAK-3131: Description: During a RepositorySidegrade migration it may happen that DocumentNodeStore has to write a blob that has been created in another instance, but fails because it has been optimized for the usual scenario where there is just one instance. (was: During an Oak2Oak migration it may happen that DocumentNodeStore has to write a blob that has been created in another instance, but fails because it has been optimized for the usual scenario where there is just one instance.) > DocumentNodeStore doesn't serialize blobs that have been created in a > different store > - > > Key: OAK-3131 > URL: https://issues.apache.org/jira/browse/OAK-3131 > Project: Jackrabbit Oak > Issue Type: Bug > Components: core, upgrade >Affects Versions: 1.2.2, 1.3.2, 1.0.17 >Reporter: Manfred Baedke >Assignee: Manfred Baedke > > During a RepositorySidegrade migration it may happen that DocumentNodeStore > has to write a blob that has been created in another instance, but fails > because it has been optimized for the usual scenario where there is just one > instance. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
