jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OAK-7570) [DirectBinaryAccess][DISCUSS] How to access HttpBlobProvider from oak-jcr
Date Tue, 03 Jul 2018 11:21:00 GMT

     [ https://issues.apache.org/jira/browse/OAK-7570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Marcel Reutegger updated OAK-7570:
----------------------------------
    Component/s:     (was: blob-plugins)
                 jcr
        Summary: [DirectBinaryAccess][DISCUSS] How to access HttpBlobProvider from oak-jcr
 (was: [DirectBinaryAccess][DISCUSS] Client access via DataStoreBlobStore directly)

I'd like to focus a bit more on the initial topic of this issue and changed the summary to
better reflect that.

The alternative outlined in the first comment is implemented in this github branch: https://github.com/mreutegg/jackrabbit-oak/tree/direct-binary-access-with-bypass

Comparison with oak trunk: https://github.com/apache/jackrabbit-oak/compare/trunk...mreutegg:direct-binary-access-with-bypass

Comparison with Matt's PR: https://github.com/mattvryan/jackrabbit-oak/compare/direct-binary-access...mreutegg:direct-binary-access-with-bypass

The changes do not touch any of the other areas discussed in the context of the direct binary
access PR (e.g. the feature is still exposed as an extension of the Session). With these changes
commits to MutableRoot, DocumentNodeStore and SegmentNodeStore can be reverted. SessionImpl
is simplified by avoiding null checks for the HttpBlobProvider. The HttpBlobProvider is passed
to the SessionContext via the Whiteboard.

> [DirectBinaryAccess][DISCUSS] How to access HttpBlobProvider from oak-jcr
> -------------------------------------------------------------------------
>
>                 Key: OAK-7570
>                 URL: https://issues.apache.org/jira/browse/OAK-7570
>             Project: Jackrabbit Oak
>          Issue Type: Technical task
>          Components: jcr
>            Reporter: Matt Ryan
>            Assignee: Matt Ryan
>            Priority: Major
>
> Open discussion related to OAK-7569:
> The [original pull request|https://github.com/apache/jackrabbit-oak/pull/88] proposes
changes to oak-api, oak-segment-tar, oak-store-document, oak-core, and oak-jcr as well as
oak-blob-plugins, oak-blob-cloud, and oak-blob-azure.  Would it be possible / better to keep
the changes local to the oak-blob-* bundles and avoid making changes throughout the stack?



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

Mime
View raw message