[jira] [Updated] (HDFS-4757) Update FSDirectory#inodeMap when replacing an INodeDirectory while setting quota
[ https://issues.apache.org/jira/browse/HDFS-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-4757: Affects Version/s: 3.0.0 Status: Patch Available (was: Open) > Update FSDirectory#inodeMap when replacing an INodeDirectory while setting > quota > > > Key: HDFS-4757 > URL: https://issues.apache.org/jira/browse/HDFS-4757 > Project: Hadoop HDFS > Issue Type: Bug >Affects Versions: 3.0.0 >Reporter: Jing Zhao >Assignee: Jing Zhao >Priority: Minor > Attachments: HDFS-4757.001.patch > > > When setting quota to a directory, we may need to replace the original > directory node with a new node with the same id. We need to update the > inodeMap after the node replacement. -- 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
[jira] [Updated] (HDFS-4757) Update FSDirectory#inodeMap when replacing an INodeDirectory while setting quota
[ https://issues.apache.org/jira/browse/HDFS-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jing Zhao updated HDFS-4757: Attachment: HDFS-4757.001.patch A simple patch with unit test. > Update FSDirectory#inodeMap when replacing an INodeDirectory while setting > quota > > > Key: HDFS-4757 > URL: https://issues.apache.org/jira/browse/HDFS-4757 > Project: Hadoop HDFS > Issue Type: Bug >Reporter: Jing Zhao >Assignee: Jing Zhao >Priority: Minor > Attachments: HDFS-4757.001.patch > > > When setting quota to a directory, we may need to replace the original > directory node with a new node with the same id. We need to update the > inodeMap after the node replacement. -- 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
[jira] [Updated] (HDFS-4757) Update FSDirectory#inodeMap when replacing an INodeDirectory while setting quota
[ https://issues.apache.org/jira/browse/HDFS-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-4757: - Component/s: namenode Hadoop Flags: Reviewed +1 patch looks good. > Update FSDirectory#inodeMap when replacing an INodeDirectory while setting > quota > > > Key: HDFS-4757 > URL: https://issues.apache.org/jira/browse/HDFS-4757 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 3.0.0 >Reporter: Jing Zhao >Assignee: Jing Zhao >Priority: Minor > Attachments: HDFS-4757.001.patch > > > When setting quota to a directory, we may need to replace the original > directory node with a new node with the same id. We need to update the > inodeMap after the node replacement. -- 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
[jira] [Updated] (HDFS-4757) Update FSDirectory#inodeMap when replacing an INodeDirectory while setting quota
[ https://issues.apache.org/jira/browse/HDFS-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tsz Wo (Nicholas), SZE updated HDFS-4757: - Resolution: Fixed Fix Version/s: 3.0.0 Status: Resolved (was: Patch Available) I have committed this. Thanks, Jing! > Update FSDirectory#inodeMap when replacing an INodeDirectory while setting > quota > > > Key: HDFS-4757 > URL: https://issues.apache.org/jira/browse/HDFS-4757 > Project: Hadoop HDFS > Issue Type: Bug > Components: namenode >Affects Versions: 3.0.0 >Reporter: Jing Zhao >Assignee: Jing Zhao >Priority: Minor > Fix For: 3.0.0 > > Attachments: HDFS-4757.001.patch > > > When setting quota to a directory, we may need to replace the original > directory node with a new node with the same id. We need to update the > inodeMap after the node replacement. -- 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
