[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Fix Version/s: 1.0.20 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.4, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5, 1.0.20, 1.2.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Affects Version/s: (was: 1.2.3) 1.2.4 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.4, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5, 1.2.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Fix Version/s: 1.2.5 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.4, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5, 1.2.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Fix Version/s: (was: 1.3.6) 1.3.5 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Amit Jain updated OAK-3261: --- Fix Version/s: (was: 1.3.5) 1.3.6 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.6 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Affects Version/s: (was: 1.0.18) (was: 1.3.3) 1.3.4 1.0.19 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Fix Version/s: (was: 1.4) 1.3.5 > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.4, 1.0.19 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.3.5 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Attachment: OAK-3261.diff proposed patch > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.3, 1.0.18 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.4 > > Attachments: OAK-3261.diff > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (OAK-3261) consider existing locks when creating new ones
[ https://issues.apache.org/jira/browse/OAK-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-3261: Description: When creating new locks, existing locks need to be checked: - on ancestor nodes, when deep locks - on descendant nodes (Note that the check on descendant nodes might be costly as long as we have to walk to whole subtree) was: When creating new locks, existing locks need to be checked: - on ancestor nodes, when deep locks - on descendant nodes > consider existing locks when creating new ones > -- > > Key: OAK-3261 > URL: https://issues.apache.org/jira/browse/OAK-3261 > Project: Jackrabbit Oak > Issue Type: Sub-task > Components: jcr >Affects Versions: 1.2.3, 1.3.3, 1.0.18 >Reporter: Julian Reschke >Assignee: Julian Reschke > Fix For: 1.4 > > > When creating new locks, existing locks need to be checked: > - on ancestor nodes, when deep locks > - on descendant nodes > (Note that the check on descendant nodes might be costly as long as we have > to walk to whole subtree) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
