[jira] [Updated] (HDFS-5284) Flatten INode hierarchy

2017-01-06 Thread Junping Du (JIRA)

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

Junping Du updated HDFS-5284:
-
Target Version/s:   (was: 2.8.0)

> Flatten INode hierarchy
> ---
>
> Key: HDFS-5284
> URL: https://issues.apache.org/jira/browse/HDFS-5284
> Project: Hadoop HDFS
>  Issue Type: Improvement
>  Components: namenode
>Affects Versions: 2.4.0
>Reporter: Tsz Wo Nicholas Sze
>Assignee: Jing Zhao
>
> Currently, we have a complicated inode hierarchy for representing different 
> states of a file or a directory.  For example,  when a file is being created, 
> it is represented by an INodeFileUnderConstruction.  When a file is being 
> closed, the inode is replaced by an INodeFile.  If it is reopened for append, 
> the inode is replaced again by an INodeFileUnderConstruction.  This JIRA is 
> to flatten the inode hierarchy.  We may also improve the performance by 
> eliminating the inode replacement in runtime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-5284) Flatten INode hierarchy

2015-06-29 Thread Vinod Kumar Vavilapalli (JIRA)

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

Vinod Kumar Vavilapalli updated HDFS-5284:
--
Target Version/s: 2.8.0  (was: 2.4.0)

Moving features/enhancements out of previously closed releases into the next 
minor release 2.8.0.

 Flatten INode hierarchy
 ---

 Key: HDFS-5284
 URL: https://issues.apache.org/jira/browse/HDFS-5284
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Affects Versions: 2.4.0
Reporter: Tsz Wo Nicholas Sze
Assignee: Jing Zhao

 Currently, we have a complicated inode hierarchy for representing different 
 states of a file or a directory.  For example,  when a file is being created, 
 it is represented by an INodeFileUnderConstruction.  When a file is being 
 closed, the inode is replaced by an INodeFile.  If it is reopened for append, 
 the inode is replaced again by an INodeFileUnderConstruction.  This JIRA is 
 to flatten the inode hierarchy.  We may also improve the performance by 
 eliminating the inode replacement in runtime.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


Auto-Re: [jira] [Updated] (HDFS-5284) Flatten INode hierarchy

2015-06-29 Thread wsb
您的邮件已收到!谢谢!

[jira] [Updated] (HDFS-5284) Flatten INode hierarchy

2014-02-14 Thread Jing Zhao (JIRA)

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

Jing Zhao updated HDFS-5284:


 Target Version/s: 2.4.0
Affects Version/s: 2.4.0

 Flatten INode hierarchy
 ---

 Key: HDFS-5284
 URL: https://issues.apache.org/jira/browse/HDFS-5284
 Project: Hadoop HDFS
  Issue Type: Improvement
  Components: namenode
Affects Versions: 2.4.0
Reporter: Tsz Wo (Nicholas), SZE
Assignee: Tsz Wo (Nicholas), SZE

 Currently, we have a complicated inode hierarchy for representing different 
 states of a file or a directory.  For example,  when a file is being created, 
 it is represented by an INodeFileUnderConstruction.  When a file is being 
 closed, the inode is replaced by an INodeFile.  If it is reopened for append, 
 the inode is replaced again by an INodeFileUnderConstruction.  This JIRA is 
 to flatten the inode hierarchy.  We may also improve the performance by 
 eliminating the inode replacement in runtime.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)