You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Kai Sasaki (JIRA)" <ji...@apache.org> on 2017/04/02 13:42:42 UTC
[jira] [Updated] (HADOOP-13665) Erasure Coding codec should support
fallback coder
[ https://issues.apache.org/jira/browse/HADOOP-13665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kai Sasaki updated HADOOP-13665:
--------------------------------
Attachment: HADOOP-13665.08.patch
> Erasure Coding codec should support fallback coder
> --------------------------------------------------
>
> Key: HADOOP-13665
> URL: https://issues.apache.org/jira/browse/HADOOP-13665
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: io
> Reporter: Wei-Chiu Chuang
> Assignee: Kai Sasaki
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HADOOP-13665.01.patch, HADOOP-13665.02.patch, HADOOP-13665.03.patch, HADOOP-13665.04.patch, HADOOP-13665.05.patch, HADOOP-13665.06.patch, HADOOP-13665.07.patch, HADOOP-13665.08.patch
>
>
> The current EC codec supports a single coder only (by default pure Java implementation). If the native coder is specified but is unavailable, it should fallback to pure Java implementation.
> One possible solution is to follow the convention of existing Hadoop native codec, such as transport encryption (see {{CryptoCodec.java}}). It supports fallback by specifying two or multiple coders as the value of property, and loads coders in order.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org