[
https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17184184#comment-17184184
]
Bharat Viswanadham commented on HDDS-4097:
------------------------------------------
{quote}Why do we need that specific settings at all? IF we can provide 100% AWS
s3 compatibility with the new approach why is it required to be optional? Do
you see any disadvantage of the new approach?
{quote}
S3, does allow creating files and directories with the same name and also it
does not follow/check any filesystem semantics. So, if we want object-store
semantics, this flag provides a fall back. So, I think we still need this, as
We cannot make 100% AWS S3 compatibility.
{quote}Prefix table effort creates prefixes for each parent directories
(AFAIK). Do we need this code after a working prefix table? Will this concept
be changed after using prefix table?
{quote}
Still normalize path code change will be needed, but we don't need special
distinguish for file and directory like we have today "/" if it ends that means
it is a directory. Prefix table work changes the format it stores the key, but
to break the path in to components still we need to normalize path when
ozone.om.enable.filesystem.paths is enabled.
> 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
