Kai Zheng commented on HADOOP-13715:

bq. are we sure that a simple boolean is actually the value desired?
People may want to expose {{ErasureCodingPolicy getErasureCodingPolicy()}} 
other than the simple boolean value because it can contain more info and be 
flexible. But it may require that ErasureCodingPolicy concept be defined in 
hadoop level other than just for HDFS, however since most hadoop file system 
won't need the concept so it doesn't sound like elegant. So far as I can view, 
isErasureCoded is good to have as the existing isEncrypted. If applications 
need drill into the erasure coding internal, it will need to depend on the HDFS 
client API then.

It does be a good chance to add/change the API at this time, targeting the 3.0 

> Add isErasureCoded() API to FileStatus class
> --------------------------------------------
>                 Key: HADOOP-13715
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13715
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs
>    Affects Versions: 3.0.0-alpha1
>            Reporter: Wei-Chiu Chuang
>            Assignee: Wei-Chiu Chuang
> Per the discussion in 
> [HDFS-10971|https://issues.apache.org/jira/browse/HDFS-10971?focusedCommentId=15567108&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15567108]
>  I would like to add a new API {{isErasureCoded()}} to {{FileStatus}} so that 
> tools and downstream applications can tell if it needs to treat a file 
> differently.
> Hadoop tools that can benefit from this effort include: distcp and 
> teragen/terasort.
> Downstream applications such as flume or hbase may also benefit from it.

This message was sent by Atlassian JIRA

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

Reply via email to