[
https://issues.apache.org/jira/browse/HDDS-4155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17190803#comment-17190803
]
Bharat Viswanadham edited comment on HDDS-4155 at 9/4/20, 4:05 PM:
-------------------------------------------------------------------
{quote}I am wondering what is the problem with it. It seems that Hadoop
Compatible File System can handle this and display both.
{quote}
Not tested my self, I think here to say S3AFileSystem supports it not every
Hadoop Compatible FileSystem supports it(Example below). My guess is as S3A
does not have control over AWS S3 implementation, might be they cannot avoid
this. But in the Ozone case, during KeyCommit we can catch this, and block it.
So, the question is do we want to support what kind of semantics in Ozone?
{quote}It seems to be very strange for me as this is something which should be
avoid with posix fs, but if hadoop can support it...
{quote}
An Example, HDFS disallows this, it does not allow file and a directory with
the same name in a path.
was (Author: bharatviswa):
{quote}I am wondering what is the problem with it. It seems that Hadoop
Compatible File System can handle this and display both.
{quote}
Not tested my self, I think here to say S3AFileSystem supports it not every
Hadoop Compatible FileSystem supports it(Example below). My guess is as S3A
does not have control over AWS S3 implementation, might be they cannot avoid
this. But in the Ozone case, during KeyCommit we can catch this, and block it.
So, the question is do we want to support such semantics in Ozone?
{quote}It seems to be very strange for me as this is something which should be
avoid with posix fs, but if hadoop can support it...
{quote}
An Example, HDFS disallows this, it does not allow file and a directory with
the same name in a path.
> Directory and filename can end up with same name in a path
> ----------------------------------------------------------
>
> Key: HDDS-4155
> URL: https://issues.apache.org/jira/browse/HDDS-4155
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
>
> Scenario:
> Create Key via S3, and Create Directory through Fs.
> # open key -> /a/b/c
> # CreateDirectory -> /a/b/c
> # CommitKey -> /a/b/c
> So, now in Ozone we will have directory and file with name "c"
> When created through Fs interface.
> # create file -> /a/b/c
> # CreateDirectory -> /a/b/c
> # CommitKey -> /a/b/c
> So, now in Ozone we will have directory and file with name "c"
>
> # InitiateMPU /a/b/c
> # Create Part1 /a/b/c
> # Commit Part1 /a/b/c
> # Create Directory /a/b/c
> # Complete MPU /a/b/c
> So, now in Ozone, we will have directory and file with name "c". In MPU this
> is one example scenario.
>
> Few proposals/ideas to solve this:
> # Check during commit whether a directory already exists with same name. But
> disadvantage is after user uploads the entire data during last stage we fail.
> (File system with create in progress acts similarly. Scenario: 1. vi t1 2.
> mkdir t1 3. Save t1: (Fail:"t1" is a directory)
> # During create directory check are there any open key creation with same
> name and fail.
>
> Any of the above approaches are not final, this Jira is opened to discuss
> this issue and come up with solution.
--
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
