Return-Path: X-Original-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A7B3C17889 for ; Mon, 20 Apr 2015 05:30:59 +0000 (UTC) Received: (qmail 41562 invoked by uid 500); 20 Apr 2015 05:30:59 -0000 Delivered-To: apmail-hadoop-hdfs-issues-archive@hadoop.apache.org Received: (qmail 41492 invoked by uid 500); 20 Apr 2015 05:30:59 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hdfs-issues@hadoop.apache.org Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 41478 invoked by uid 99); 20 Apr 2015 05:30:59 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Apr 2015 05:30:59 +0000 Date: Mon, 20 Apr 2015 05:30:59 +0000 (UTC) From: "Kai Sasaki (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (HDFS-8136) Client gets and uses EC schema when reads and writes a stripping file MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HDFS-8136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kai Sasaki updated HDFS-8136: ----------------------------- Attachment: HDFS-8136.3.patch > Client gets and uses EC schema when reads and writes a stripping file > --------------------------------------------------------------------- > > Key: HDFS-8136 > URL: https://issues.apache.org/jira/browse/HDFS-8136 > Project: Hadoop HDFS > Issue Type: Sub-task > Affects Versions: HDFS-7285 > Reporter: Kai Zheng > Assignee: Kai Sasaki > Attachments: HDFS-8136.1.patch, HDFS-8136.2.patch, HDFS-8136.3.patch > > > Discussed with [~umamaheswararao] and [~vinayrpet], in client when reading and writing a stripping file, it can invoke a separate call to NameNode to request the EC schema associated with the EC zone where the file is in. Then the schema can be used to guide the reading and writing. Currently it uses hard-coded values. > Optionally, as an optimization consideration, client may cache schema info per file or per zone or per schema name. We could add schema name in {{HdfsFileStatus}} for that. -- This message was sent by Atlassian JIRA (v6.3.4#6332)