hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "SammiChen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11152) Start erasure coding policy ID number from 1 instead of 0 to void potential unexpected errors
Date Thu, 22 Dec 2016 02:30:58 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768801#comment-15768801
] 

SammiChen commented on HDFS-11152:
----------------------------------

I just find one FSImage issue regarding erasure coding. I created JIRA HDFS-11268. I think
I should solve HDFS-11268 first, then come back to this JIRA.

> 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
>    Affects Versions: 3.0.0-alpha1
>            Reporter: SammiChen
>            Assignee: SammiChen
>              Labels: hdfs-ec-3.0-must-do
>         Attachments: HDFS-11152-v1.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.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message