hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7859) Erasure Coding: Persist EC schemas in NameNode
Date Mon, 27 Apr 2015 19:02:38 GMT

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

Allen Wittenauer commented on HDFS-7859:

I did some playing with a test jira this morning.  IIRC, It looks like submit patch is only
available to the requester and the assignee when the jira is in the 'in progress' status.
 The 'in progress' status can only be changed by the assignee and/or the requester.  I then
thought well, I'll force it through jenkins... but test-patch.sh is "smart" in that it will
only process jiras that are in patch available status.  So while I could have changed the
meta info in the JIRA to force it to kick off, I didn't want to freak anyone out more than
I already had by popping up in here.  I thought it was going to be an easy/quick test. :(

Running test-patch.sh as a developer against this JIRA # *does* run it against the HDFS-7285
branch though, as expected.  :D  (I had tested patches against branch-2, but hadn't had a
chance to test against a dev branch... so this updated last night and thought it'd be a good
guinea pig)

> Erasure Coding: Persist EC schemas in NameNode
> ----------------------------------------------
>                 Key: HDFS-7859
>                 URL: https://issues.apache.org/jira/browse/HDFS-7859
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Kai Zheng
>            Assignee: Xinwei Qin 
>         Attachments: HDFS-7859-HDFS-7285.002.patch, HDFS-7859.001.patch, HDFS-7859.002.patch
> In meetup discussion with [~zhz] and [~jingzhao], it's suggested that we persist EC schemas
in NameNode centrally and reliably, so that EC zones can reference them by name efficiently.

This message was sent by Atlassian JIRA

View raw message