[jira] [Updated] (JCR-4387) Wrong error message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4387: Attachment: JCR-4387.diff > Wrong error message when same-name-sibling is prevented on import >

[jira] [Commented] (JCR-4387) Wrong error message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691699#comment-16691699 ] Julian Reschke commented on JCR-4387: - Test case moved into separate class:

[jira] [Updated] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4387: Fix Version/s: 2.18 > Incorrect exception message when same-name-sibling is prevented on import >

[jira] [Updated] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4387: Labels: candidate_jcr_2_16 (was: ) > Incorrect exception message when same-name-sibling is

[jira] [Updated] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4387: Summary: Incorrect exception message when same-name-sibling is prevented on import (was: Wrong

[jira] [Updated] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated JCR-4387: Priority: Minor (was: Major) > Incorrect exception message when same-name-sibling is prevented on

[jira] [Resolved] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke resolved JCR-4387. - Resolution: Fixed Fix Version/s: 2.17.7 > Incorrect exception message when

[jira] [Commented] (JCR-4387) Incorrect exception message when same-name-sibling is prevented on import

[ https://issues.apache.org/jira/browse/JCR-4387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691719#comment-16691719 ] Julian Reschke commented on JCR-4387: - trunk: [r1846896|http://svn.apache.org/r1846896] > Incorrect

Intent to backport OAK-7867 to Oak 1.8 and 1.6

Hi, I intend to backport OAK-7867 to Oak 1.8 and 1.6. This fixes an issue that can cause sever data loss with the segment node store. There is a medium to high risk with this backport as it touches some of the core parts of the segment node store. To mitigate the risk we ran a 14 days longevity

Re: Intent to backport OAK-7867 to Oak 1.8 and 1.6

+1 On Mon, 19 Nov 2018 at 17:50, Michael Dürig wrote: > Hi, > > I intend to backport OAK-7867 to Oak 1.8 and 1.6. This fixes an issue > that can cause sever data loss with the segment node store. There is a > medium to high risk with this backport as it touches some of the core > parts of the

Re: Intent to backport OAK-7867 to Oak 1.8 and 1.6

On Mon, Nov 19, 2018 at 11:50 AM Michael Dürig wrote: > > Hi, > > I intend to backport OAK-7867 to Oak 1.8 and 1.6. This fixes an issue > that can cause sever data loss with the segment node store. There is a > medium to high risk with this backport as it touches some of the core > parts of the