hadoop-hdfs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HDFS-4357) After calling replaceSelf, further operations that should be applied on the new INode may be wrongly applied to the original INode
Date Fri, 04 Jan 2013 10:48:12 GMT

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

Tsz Wo (Nicholas), SZE resolved HDFS-4357.
------------------------------------------

       Resolution: Fixed
    Fix Version/s: Snapshot (HDFS-2802)

I have committed this.  Thanks, Jing!
                
> After calling replaceSelf, further operations that should be applied on the new INode
may be wrongly applied to the original INode
> ----------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HDFS-4357
>                 URL: https://issues.apache.org/jira/browse/HDFS-4357
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Jing Zhao
>            Assignee: Jing Zhao
>             Fix For: Snapshot (HDFS-2802)
>
>         Attachments: HDFS-4357.001.patch, HDFS-4357.002.patch, HDFS-4357.003.patch
>
>
> An example is in INode#setModificationTime, if the INode is an instance of INodeDirectory,
after replacing itself with a new INodeDirectoryWithSnapshot, the change of the modification
time should happen in the new INodeDirectoryWithSnapshot instead of the original INodeDirectory.

--
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