hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4469) Inculde file id in these ClientProtocol RPCs which were originally only using path to identify a file
Date Mon, 25 Mar 2013 23:09:16 GMT

     [ https://issues.apache.org/jira/browse/HDFS-4469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Suresh Srinivas resolved HDFS-4469.
-----------------------------------

    Resolution: Invalid

Given the design from HDFS-4489, a variant of protocol methods to include INodeID to identify
the inode is no longer required. Existing path will be used for carrying the inode information
and will be part of HDFS-4434.
                
> Inculde file id in these ClientProtocol RPCs which were originally only using path to
identify a file
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4469
>                 URL: https://issues.apache.org/jira/browse/HDFS-4469
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>    Affects Versions: 3.0.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>
> Like HDFS-4340(add fileId to addBlock), this JIRA is to track the change to add fileId
to other RPC calls, such as append, complete and etc.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message