Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pig-dev@hadoop.apache.org
Message-ID: <143835218.621711270082067256.JavaMail.jira@brutus.apache.org>
Date: Thu, 1 Apr 2010 00:34:27 +0000 (UTC)
From: "Chao Wang (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Subject: [jira] Updated: (PIG-1342) [Zebra] Avoid making unnecessary name
 node calls for writes in Zebra
In-Reply-To: <1671334511.593131269994467181.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/PIG-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chao Wang updated PIG-1342:
---------------------------

    Attachment: PIG-1342.patch

> [Zebra] Avoid making unnecessary name node calls for writes in Zebra
> --------------------------------------------------------------------
>
>                 Key: PIG-1342
>                 URL: https://issues.apache.org/jira/browse/PIG-1342
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.6.0, 0.7.0
>            Reporter: Chao Wang
>            Assignee: Chao Wang
>             Fix For: 0.8.0
>
>         Attachments: PIG-1342.patch
>
>
> Currently, table and column group level meta data is extracted from job configuration object and written onto HDFS disk within checkOutputSpec(). Later on, writers at back end will open these files to access the meta data for doing writes. This puts extra load to name node since all writers need to make name node calls to open files. 
> We propose the following approach to this problem:
> For writers at back end, they extract meta information from job configuration object directly, rather than making name node calls and going to HDFS disk to fetch the information.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.