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

Arpit Agarwal edited comment on HDDS-4097 at 8/31/20, 5:27 PM:
---------------------------------------------------------------

bq. Even when the flag is false, intermediate directory creation should be 
supported, without any check for file system semantics.
No, FS interaction with data ingested via S3 should simply not be supported 
when the flag is off. Let's not try to support some halfway half-baked option, 
it will be hard to get right.

To clarify a bit more, how do you message half support to a potential user of 
Ozone? The FS side expects a hierarchical directory tree and FS operations to 
work like HDFS. The S3 side expects a flat key value namespace. It is one or 
the other, there is no in-between option.


was (Author: arpitagarwal):
bq. Even when the flag is false, intermediate directory creation should be 
supported, without any check for file system semantics.
No, FS interaction with data ingested via S3 should simply not be supported 
when the flag is off. Let's not try to support some halfway half-baked option, 
it will be hard to get right.

> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org

Reply via email to