[
https://issues.apache.org/jira/browse/OAK-1963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15277825#comment-15277825
]
Thomas Mueller commented on OAK-1963:
-------------------------------------
So this would only give access to data that is already available (another _way_
to access the same data). The problem is that an URL can be more easily copied
because it is shorter. So it is more of an encapsulation / API design
(philosophy) problem than an access right problem. Same as for JCR-3534.
It would be good to have more details on the exact use case. I assume it's just
for Amazon S3 right now. Where is the URL used (is it rendered on the page for
example), does it need to be available for any kind of user / session, or could
the feature be restricted to certain cases (ACLs).
More details for justification would be nice. Do we want to improve
performance, do we know how much it would bring, or do we want to reduce cost
(reduce traffic to a web server), or both.
One option might be a new API to get the a node path + property name + index
(for multi-valued properties) to an S3 URL, and not directly for a
javax.jcr.Binary or Value. So that access to the path and property could be
checked.
> Expose URL for Blob source
> ---------------------------
>
> Key: OAK-1963
> URL: https://issues.apache.org/jira/browse/OAK-1963
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Pralaypati Ta
> Assignee: Chetan Mehrotra
> Labels: datastore
> Fix For: 1.6
>
>
> In certain scenarios for performance reasons its desirable to have direct
> access to the Blob source.
> For e.g. if using a FileDataStore having a direct access to the native file
> system path of the blob (if not stored in chunks) is more useful than
> repository path e.g. native tools don't understand repository path, instead
> file system path can be passed directly to native tools for processing binary.
> Another usecase being ability exposed signed S3 url which would allow access
> to binary content directly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
