[
https://issues.apache.org/jira/browse/HDFS-8854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14653252#comment-14653252
]
Walter Su commented on HDFS-8854:
---------------------------------
In the world of HDFS, cellSize always goes around with ecSchema. Why not just
move cellSize inside ecSchema?
Advantages:
1. shorter args list, cleaner code.
2. store one field in BlockInfoStriped, instead of two fields. Less memory
usage.
Other influences(not disadvantages, just influences):
1. cellSize is not needed by coder in hadoop-common. It doesn't matter. Coder
can just ignore it.
2. cellSize is configured in server side, instead of client side. cellSize is
not given by user. Arbitrary values of cellSize, like 63k, 67k is meaningless.
cellSize can be 64k, 128k, 256k,... ecSchema is loaded from file in server
side, together with cellSize.
> Erasure coding: Move cellSize inside ECSchema
> ---------------------------------------------
>
> Key: HDFS-8854
> URL: https://issues.apache.org/jira/browse/HDFS-8854
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Walter Su
> Assignee: Walter Su
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
