Steve Loughran commented on HADOOP-13715:

# I'll be expecting filesystem.md to be updated with this.
# FileStatus instances get sent over the wire a lot. I'd be nice if any new 
bitfields didn't add too much to the weight of an instance. It's too late to 
move existing booleans (isDirectory, ....) to being bitmasks in a larger 
number, but this may be the time to start, assuming we will continue to add 
more booleans (isEncrypted, isErasureCoded, ...).
# are we sure that a simple boolean is actually the value desired?  That is: 
there is never going to be any other outcome at some point in the future. As if 
it may happen (i.e. someone can see a clear roadmap to adding more detail on 
erasure coding internals), then again, bitmask or enum of erasure coding 
details calls out

> 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