[ https://issues.apache.org/jira/browse/HDFS-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13983286#comment-13983286 ]
Steve Loughran commented on HDFS-6294: -------------------------------------- There's a test for this in HADOOP-9361 which attempts to [rename a file being appended to|https://github.com/steveloughran/hadoop-trunk/blob/stevel/HADOOP-9361-filesystem-contract/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/fs/contract/AbstractAppendContractTest.java#L113]. Presumably that test will pass once this patch has gone through? > Use INode IDs to avoid conflicts when a file open for write is renamed > ---------------------------------------------------------------------- > > Key: HDFS-6294 > URL: https://issues.apache.org/jira/browse/HDFS-6294 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode > Affects Versions: 0.20.1 > Reporter: Colin Patrick McCabe > Assignee: Colin Patrick McCabe > Attachments: HDFS-6294.001.patch > > > Now that we have a unique INode ID for each INode, clients with files that > are open for write can use this unique ID rather than a file path when they > are requesting more blocks or closing the open file. This will avoid > conflicts when a file which is open for write is renamed, and another file > with that name is created. -- This message was sent by Atlassian JIRA (v6.2#6252)