jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Marth (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3261) consider existing locks when creating new ones
Date Fri, 21 Aug 2015 09:44:46 GMT

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

Michael Marth commented on OAK-3261:
------------------------------------

{quote}
Note that the check on descendant nodes might be costly as long as we have to walk to whole
subtree 
{quote}
Could we do something analogous to the permission tree structure to make it efficient?

> 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)

Mime
View raw message