[
https://issues.apache.org/jira/browse/HADOOP-10948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14302051#comment-14302051
]
David Dobbins commented on HADOOP-10948:
----------------------------------------
Is there an avenue for maintaining backwards compatibility? It seems the only
risk is for directories already created in swift with SwiftNativeFileSystem.
Would it suffice to only create new directories using the trailing-slash model
but to recognize either model for the purposes of reading existing directories?
> SwiftNativeFileSystem's directory is incompatible with Swift and Horizon
> ------------------------------------------------------------------------
>
> Key: HADOOP-10948
> URL: https://issues.apache.org/jira/browse/HADOOP-10948
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/swift
> Affects Versions: 3.0.0
> Reporter: Kazuki OIKAWA
> Assignee: Kazuki OIKAWA
> Attachments: HADOOP-10948-2.patch, HADOOP-10948.patch
>
>
> SwiftNativeFileSystem's directory representation is zero-byte file.
> But in Swift / Horizon, directory representation is a trailing-slash.
> This incompatibility has the following issues.
> * SwiftNativeFileSystem can't see pseudo-directory made by OpenStack Horizon
> * Swift/Horizon can't see pseudo-directory made by SwiftNativeFileSystem. But
> Swift/Horizon see a zero-byte file instead of that pseudo-directory.
> * SwiftNativeFileSystem can't see a file if there is no intermediate
> pseudo-directory object.
> * SwiftNativeFileSystem makes two objects when making a single directory
> (e.g. "hadoop fs -mkdir swift://test.test/dir/" => "dir" and "dir/" created)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
