[
https://issues.apache.org/jira/browse/HDDS-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HDDS-434.
-------------------------------------
Resolution: Fixed
Fix Version/s: 0.4.0
0.3.0
> 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
> Fix For: 0.3.0, 0.4.0
>
> 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: hdfs-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-h...@hadoop.apache.org
