[
https://issues.apache.org/jira/browse/HADOOP-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14740933#comment-14740933
]
Steve Loughran commented on HADOOP-12057:
-----------------------------------------
-1; tests failing, at least locally. But repeatedly.
{code}
TestSwiftFileSystemContract>FileSystemContractBaseTest.testRenameDirectoryMoveToExistingDirectory:417->FileSystemContractBaseTest.rename:495
Source exists expected:<false> but was:<true>
TestSwiftFileSystemContract>FileSystemContractBaseTest.testRenameDirectoryAsExistingDirectory:449->FileSystemContractBaseTest.rename:495
Source exists expected:<false> but was:<true>
{code}
That is, after the rename the source directories are still there
> swiftfs rename on partitioned file attempts to consolidate partitions
> ---------------------------------------------------------------------
>
> Key: HADOOP-12057
> URL: https://issues.apache.org/jira/browse/HADOOP-12057
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/swift
> Reporter: David Dobbins
> Assignee: David Dobbins
> Attachments: HADOOP-12057-006.patch, HADOOP-12057-008.patch,
> HADOOP-12057.007.patch, HADOOP-12057.patch, HADOOP-12057.patch,
> HADOOP-12057.patch, HADOOP-12057.patch, HADOOP-12057.patch
>
>
> In the swift filesystem for openstack, a rename operation on a partitioned
> file uses the swift COPY operation, which attempts to consolidate all of the
> partitions into a single object. This causes the rename to fail when the
> total size of all the partitions exceeds the maximum object size for swift.
> Since partitioned files are primarily created to allow a file to exceed the
> maximum object size, this bug makes writing to swift extremely unreliable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
