[
https://issues.apache.org/jira/browse/HADOOP-11244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191692#comment-14191692
]
Steve Loughran commented on HADOOP-11244:
-----------------------------------------
not thread safety: visibility of changes to the FS to your code.
Examples
# file deleted while you have the stream open for reading
# file appended to during reads
# full R/W files: changes to the contents of a file during a read
# multiple writers appending: are the appends atomic vs interleaved
that's what I was trying to say. Now, if that wasn't clear, that could go into
a patch
> The HCFS contract test testRenameFileBeingAppended doesn't do a rename
> ----------------------------------------------------------------------
>
> Key: HADOOP-11244
> URL: https://issues.apache.org/jira/browse/HADOOP-11244
> Project: Hadoop Common
> Issue Type: Bug
> Components: test
> Reporter: Noah Watkins
> Assignee: jay vyas
> Fix For: 2.6.0
>
> Attachments: HADOOP-11244.patch, HADOOP-11244.patch
>
>
> The test AbstractContractAppendTest::testRenameFileBeingAppended appears to
> assert the behavior of renaming a file opened for writing. However, the
> assertion "assertPathExists("renamed destination file does not exist",
> renamed);" fails because it appears that the file "renamed" is never created
> (ostensibly it should be the "target" file that has been renamed).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
