[ https://issues.apache.org/jira/browse/HDFS-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030852#comment-13030852 ]
Tigran Mkrtchyan commented on HDFS-487: --------------------------------------- I have implemented nfsv4.1/pNFS server and interfaced it with hdfs. The missing path to get it production ready is a unique file id and a way to access a file with it as nfs IO operations done with filehandles. Currently I maintain a path to it mapping, but this is not en elegant solution and does not survives restarts. A native hadoop way of doing that is required. > HDFS should expose a fileid to uniquely identify a file > ------------------------------------------------------- > > Key: HDFS-487 > URL: https://issues.apache.org/jira/browse/HDFS-487 > Project: Hadoop HDFS > Issue Type: New Feature > Reporter: dhruba borthakur > Assignee: dhruba borthakur > Attachments: fileid1.txt > > > HDFS should expose a id that uniquely identifies a file. This helps in > developing applications that work correctly even when files are moved from > one directory to another. A typical use-case is to make the Pluggable Block > Placement Policy (HDFS-385) use fileid instead of filename. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira