[
https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17186060#comment-17186060
]
Marton Elek commented on HDDS-4097:
-----------------------------------
When do you suggest turning on a compatibility flag? What are the reasons for
turn it on or off?
I have partial understanding, but as I understood it's better to turn it on if
I would like to use ofs/o3fs for serious things. Which would make a XOR
relationship, you can either have the good AWS compatibility or good file
system semantics.
At least this is my understanding based on the description of HDDS-3955. If I
don't enable the flag, the file which is written from fluentd + s3 couldn't be
read well from o3fs (at least some directories are missing). Therefore, I have
to enable this flag If I would like to use AWS + ofs. But I can lose the AWS
compatibility with this change.
I am wondering if it's possible to get both: AWS compatibility and full file
system semantics. For example S3g can filter out the intermediate directory key
entries if they are not explicit created. Or moving some of the normalization
to the ofs/o3fs side.
I am not sure what is the right approach, but I think giving up the AWS
compatibility is a big decision which breaks one of our promises.
What are the possible alternatives which can keep AWS compatibilty?
> 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
