[
https://issues.apache.org/jira/browse/OAK-2423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
angela updated OAK-2423:
------------------------
Description:
As discussed with [~tmueller] and [~teofili], it might be beneficial for query
performance if it was possible to determine read-access without having to
create the {{Tree}} (and thus the hierarchy). The latter (as present with
{{TreePermission.canRead}}) is suited for regular repository read operations
where the tree hierarchy is built anyway.
since {{PermissionProvider.isGranted(String oakPath, String jcrActions)}}
requires to resolve the path to properly deal with write operations, i would
suggest to evaluate if adding {{PermissionProvider.canRead(@Nonnull String
treePath, @Nullable String propertyName}} would give us some performance gain
in the query case.
initial (untested) draft attached.
was:
As discussed with [~tmueller] and [~teofili], it might be beneficial for query
performance if it was possible to determine read-access without having to
create the {{Tree{{ (and thus the hierarchy). The latter (as present with
{{TreePermission.canRead}}) is suited for regular repository read operations
where the tree hierarchy is built anyway.
since {{PermissionProvider.isGranted(String oakPath, String jcrActions)}}
requires to resolve the path to properly deal with write operations, i would
suggest to evaluate if adding {{PermissionProvider.canRead(@Nonnull String
treePath, @Nullable String propertyName}} would give us some performance gain
in the query case.
initial (untested) draft attached.
> Add PermissionProvider.canRead
> ------------------------------
>
> Key: OAK-2423
> URL: https://issues.apache.org/jira/browse/OAK-2423
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Reporter: angela
> Attachments: OAK-2423.patch
>
>
> As discussed with [~tmueller] and [~teofili], it might be beneficial for
> query performance if it was possible to determine read-access without having
> to create the {{Tree}} (and thus the hierarchy). The latter (as present with
> {{TreePermission.canRead}}) is suited for regular repository read operations
> where the tree hierarchy is built anyway.
> since {{PermissionProvider.isGranted(String oakPath, String jcrActions)}}
> requires to resolve the path to properly deal with write operations, i would
> suggest to evaluate if adding {{PermissionProvider.canRead(@Nonnull String
> treePath, @Nullable String propertyName}} would give us some performance gain
> in the query case.
> initial (untested) draft attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
