[ https://issues.apache.org/jira/browse/HADOOP-13221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-13221. ------------------------------------- Fix Version/s: 3.4.0 Resolution: Fixed I'm going to WONTFIX this -it's too expensive and nobody has really noticed we break one of the fundamental assumptions about storage > s3a create() doesn't check for an ancestor path being a file > ------------------------------------------------------------ > > Key: HADOOP-13221 > URL: https://issues.apache.org/jira/browse/HADOOP-13221 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3 > Affects Versions: 2.7.2 > Reporter: Steve Loughran > Assignee: Sean Mackrory > Priority: Major > Fix For: 3.4.0 > > Attachments: HADOOP-13321-test.patch > > > Seen in a code review. Notable that if true, this got by all the FS contract > tests —showing we missed a couple. > {{S3AFilesystem.create()}} does not examine its parent paths to verify that > there does not exist one which is a file. It looks for the destination path > if overwrite=false (see HADOOP-13188 for issues there), but it doesn't check > the parent for not being a file, or the parent of that path. > It must go up the tree, verifying that either a path does not exist, or that > the path is a directory. The scan can stop at the first entry which is is a > directory, thus the operation is O(empty-directories) and not O(directories). -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-dev-h...@hadoop.apache.org