You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Marton Elek (Jira)" <ji...@apache.org> on 2020/08/13 15:12:00 UTC
[jira] [Commented] (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=17177093#comment-17177093 ]
Marton Elek commented on HDDS-4097:
-----------------------------------
Thanks to take care bout this @bharatviswa504
I have a few questions about the design, uploaded to the https://issues.apache.org/jira/browse/HDDS-4097. Not sure where is the right place to ask, here or the PR of https://issues.apache.org/jira/browse/HDDS-4102.
Overall it looks good to me, but I am trying to understand the vision.
1. What does it mean from compatibility point of view? Will it work exactly the same way as Amazon S3? Does it mean that we start to support a different semantic when ozone.om.enable.filesystem.paths is turned on?
2. What is the long term plan, why the configuration property is needed? I mean why can't we change the default behavior? Is there any disadvantage of this approach?
3. Related to 1 + 2. Is it possible to create the intermediate "dir" keys but remove them from the list when listed from S3?
4. How does it relate to the prefix table approach?
> 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