You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Andrew Wang (JIRA)" <ji...@apache.org> on 2017/01/31 22:18:52 UTC
[jira] (HDFS-11152) Start erasure coding policy ID number from 1
instead of 0 to void potential unexpected errors
[ https://issues.apache.org/jira/browse/HDFS-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Wang updated HDFS-11152:
-------------------------------
Priority: Blocker (was: Major)
Component/s: erasure-coding
Marking ec must do's as blockers for alpha3
> Start erasure coding policy ID number from 1 instead of 0 to void potential unexpected errors
> ---------------------------------------------------------------------------------------------
>
> Key: HDFS-11152
> URL: https://issues.apache.org/jira/browse/HDFS-11152
> Project: Hadoop HDFS
> Issue Type: Task
> Components: erasure-coding
> Affects Versions: 3.0.0-alpha1
> Reporter: SammiChen
> Assignee: SammiChen
> Priority: Blocker
> Labels: hdfs-ec-3.0-must-do
> Attachments: HDFS-11152-v1.patch, HDFS-11152-v2.patch
>
>
> This task will change erasure coding policy ID number starting from 1 instead of current 0, to avoid some potential unexpected errors in codes since 0 is default value for integer variables.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org