You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/08/27 19:21:00 UTC

[jira] [Comment Edited] (HDDS-4097) S3/Ozone Filesystem inter-op

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

Bharat Viswanadham edited comment on HDDS-4097 at 8/27/20, 7:20 PM:
--------------------------------------------------------------------

AWS S3 also allows creating a key with below, which fails file system semantics.

Example:

Create Key /a/b/c/file1

CreateKey /a/b/c

 

So, now we have a file and directory with the same name which is wrong according to FS semantics, but fine with S3 semantics. So, I am not sure with this case how can we achieve 100% semantics at a time in S3 and FS.

 


was (Author: bharatviswa):
AWS S3 also allows creating a key with below, which fails file system semantics.

Example:

Create Key /a/b/c/file1

CreateKey /a/b/c

 

So, now we have a file and directory with the same name which is wrong. So, I am not sure with this case how can we achieve 100% semantics at a time in S3 and FS.

 

> S3/Ozone Filesystem inter-op
> ----------------------------
>
>                 Key: HDDS-4097
>                 URL: https://issues.apache.org/jira/browse/HDDS-4097
>             Project: Hadoop Distributed Data Store
>          Issue Type: New Feature
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>         Attachments: Ozone FileSystem Paths Enabled.docx, Ozone filesystem path enabled.xlsx
>
>
> This Jira is to implement changes required to use Ozone buckets when data is ingested via S3 and use the bucket/volume via OzoneFileSystem. Initial implementation for this is done as part of HDDS-3955. There are few API's which have missed the changes during the implementation of HDDS-3955. 
> Attached design document which discusses each API,  and what changes are required.
> Excel sheet has information about each API, from what all interfaces the OM API is used, and what changes are required for the API to support inter-operability.
> Note: The proposal for delete/rename is still under discussion, not yet finalized. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org