[
https://issues.apache.org/jira/browse/HDDS-4097?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17188536#comment-17188536
]
Marton Elek commented on HDDS-4097:
-----------------------------------
[~arp] It was discussed with more details during the community sync (the
recording is shared in the ozone-dev mailing list).
In short, my proposal is the following:
1. Using simple, acceptable key names (/a/b/c, /a/b/c/d) *both s3 and HCFS
should work out-of-the box, without any additional settings*. (Based on my
understanding this is not true today as we need to turn on
`ozone.om.enable.filesystem.paths` to get intermediate directories)
2. There are some conflicts between AWS S3 / HCFS interface. We need a new
option to express how to resolve the conflicts. Let's say we have
ozone.key.compatibility settings.
a) ozone.key.compatibility=aws means that we enable (almost) everything which
is enabled by aws s3, but we couldn't show all the keys in the hadoop
interaface. For example if directory and key are created with the same prefix
(possible with AWS S3), HCFS will show only the directory, not the key.
b) ozone.key.compatibility=hadoop is the opposite, we can validate the path,
and throw an exception on s3 interface if dir/key are created with the same name
> 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
