jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Klimetschek (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-7569) Direct Binary Access
Date Wed, 08 Aug 2018 16:26:00 GMT

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

Alexander Klimetschek commented on OAK-7569:
--------------------------------------------

AuthorizablePropertiesImpl: Good to be confirmed. When I followed the call hierachy, there
were many places that used DEFAULT (IIRC for the UserManagerImpl constructor) and it wasn‘t
clear which ones are actually used at normal runtime (and I skipped any test usages).

Limitation/documentation: fair enough. So the places that we support are getProperty().[getValue().]getBinary(),
as well as the equivalent multivalue methods (if anyone really uses multivalue binary properties
;-). Any other „normal“ Binary read case that I missed?

One thought: if we don‘t have a BlobAccessProvider available, could we return a Binary that
does not implement BinaryDownload? Then it would be clear to developers they used an unsupported
access path.

We need documentation for the oak docs anyway, not sure if there is anything yet. Happy to
add something. Where would I add this in the navigation tree?

> Direct Binary Access
> --------------------
>
>                 Key: OAK-7569
>                 URL: https://issues.apache.org/jira/browse/OAK-7569
>             Project: Jackrabbit Oak
>          Issue Type: New Feature
>          Components: api, blob-cloud, blob-cloud-azure, blob-plugins
>            Reporter: Matt Ryan
>            Assignee: Matt Ryan
>            Priority: Major
>         Attachments: OAK-7569-api-javadoc-improvements.patch
>
>
> Provide a direct binary access feature to Oak which allows an authenticated client to
create or download blobs directly to/from the blob store, assuming the authenticated user
has appropriate permission to do so. The primary value of this feature is that the I/O of
transferring large binary files to or from the blob store can be offloaded entirely from Oak
and performed directly between a client application and the blob store.
> This feature is described in more detail [on the Oak wiki|https://wiki.apache.org/jackrabbit/Direct%20Binary%20Access].
> This feature is similar in functionality to OAK-6575.  It adds the capability to also
upload directly to storage via preauthorized URLs in addition to downloading directly from
storage via preauthorized URLs.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message