[ https://issues.apache.org/jira/browse/HDDS-4163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham updated HDDS-4163: ------------------------------------- Summary: Enable filesystem semantics on bucket during creation of bucket (was: Enable filesystem semantics on bucket during creation) > Enable filesystem semantics on bucket during creation of bucket > --------------------------------------------------------------- > > Key: HDDS-4163 > URL: https://issues.apache.org/jira/browse/HDDS-4163 > Project: Hadoop Distributed Data Store > Issue Type: Bug > Reporter: Bharat Viswanadham > Assignee: Bharat Viswanadham > Priority: Major > > HDDS-3955 added a config to ozoneManager ozone.om.enable.filesystem.paths to > enable data ingested via S3, can be used from OFS/O3FS. > > But this has changed Semantics of AWS S3 behavior, and now paths are > considered as Unix paths. And also intermediate directories are created. This > has changed the behavior of the entire cluster. > This Jira is to provide an option for the user to create buckets that adhere > to filesystem semantics at the bucket level. In this way, in a single > cluster, there can be buckets that adhere to 100% Aws S3 semantics, and when > this is used from FS, they will not work, which is current behavior no change > in that part. When user decides to use the bucket from FS, so during creation > enable the filesystem semantics on the bucket, so that bucket can be used > from S3, and paths are considered as Unix paths and follow fs semantics. > (This is like not 100% AWS compatibility on bucket) > > Note: This option needs to be used during bucket creation time, cannot be > changed later as this can cause weird issues. > -- 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