[ https://issues.apache.org/jira/browse/HDFS-6294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13993993#comment-13993993 ]
Andrew Wang commented on HDFS-6294: ----------------------------------- +1 thanks Colin > 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 > Fix For: 2.5.0 > > Attachments: HDFS-6294.001.patch, HDFS-6294.002.patch, > HDFS-6294.003.patch, HDFS-6294.004.patch, HDFS-6294.005.patch, > HDFS-6294.005.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)