[
https://issues.apache.org/jira/browse/HDDS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16632162#comment-16632162
]
Anu Engineer commented on HDDS-434:
-----------------------------------
{quote}Most non-AWS S3 endpoints support only path access; avoids requiring
DNS. AWS SDK makes it optional; {{fs.s3a.path.style.access}} turns it off on
S3A. Recommend: postpone.
{quote}
This is really good to know. I was the one who insisted that we have this done
since most of the AWS docs seem to have written like this. We will postpone
this feature, or not test this too much.
> Provide an s3 compatible REST api for ozone objects
> ---------------------------------------------------
>
> Key: HDDS-434
> URL: https://issues.apache.org/jira/browse/HDDS-434
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Reporter: Elek, Marton
> Assignee: Elek, Marton
> Priority: Major
> Attachments: S3Gateway.pdf
>
>
> S3 REST api is the de facto standard for object stores. Many external tools
> already support it.
> This issue is about creating a new s3gateway component which implements (most
> part of) the s3 API using the internal RPC calls.
> Some part of the implementation is very straightforward: we need a new
> service with usual REST stack and we need to implement the most commont
> GET/POST/PUT calls. Some other (Authorization, multi-part upload) are more
> tricky.
> Here I suggest to create an evaluation: first we can implement a skeleton
> service which could support read only requests without authorization and we
> can define proper specification for the upload part / authorization during
> the work.
> As of now the gatway service could be a new standalone application (eg. ozone
> s3g start) later we can modify it to work as s DatanodePlugin similar to the
> existing object store plugin.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
