Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Mar 2017 23:45:42 +0000 (UTC)
From: "Andrew Wang (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13058424.1490226301000.94914.1490226342023@Atlassian.JIRA>
In-Reply-To: <JIRA.13058424.1490226301000@Atlassian.JIRA>
References: <JIRA.13058424.1490226301000@Atlassian.JIRA> <JIRA.13058424.1490226301660@jira-lw-us.apache.org>
Subject: [jira] [Created] (HDFS-11565) Use compact identifiers for built-in
 ECPolicies in HdfsFileStatus
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Mar 2017 23:45:48 -0000

Andrew Wang created HDFS-11565:
----------------------------------

             Summary: Use compact identifiers for built-in ECPolicies in HdfsFileStatus
                 Key: HDFS-11565
                 URL: https://issues.apache.org/jira/browse/HDFS-11565
             Project: Hadoop HDFS
          Issue Type: Improvement
          Components: erasure-coding
    Affects Versions: 3.0.0-alpha2
            Reporter: Andrew Wang
            Assignee: Andrew Wang


Discussed briefly on HDFS-7337 with Kai Zheng. Quoting our convo:

{quote}
From looking at the protos, one other question I had is about the overhead of these protos when using the hardcoded policies. There are a bunch of strings and ints, which can be kind of heavy since they're added to each HdfsFileStatus. Should we make the built-in ones identified by purely an ID, with these fully specified protos used for the pluggable policies?
{quote}

{quote}
Sounds like this could be considered separately because, either built-in policies or plugged-in polices, the full meta info is maintained either by the codes or in the fsimage persisted, so identifying them by purely an ID should works fine. If agree, we could refactor the codes you mentioned above separately.
{quote}


--
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