Mailing-List: contact pig-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pig-dev@hadoop.apache.org
Message-ID: <1510638837.700211270510467270.JavaMail.jira@brutus.apache.org>
Date: Mon, 5 Apr 2010 23:34:27 +0000 (UTC)
From: "Pradeep Kamath (JIRA)" <jira@apache.org>
To: pig-dev@hadoop.apache.org
Subject: [jira] Commented: (PIG-1330) Move pruned schema tracking logic from
 LoadFunc to core code
In-Reply-To: <1932939825.498561269555207346.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-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12853600#action_12853600 ] 

Pradeep Kamath commented on PIG-1330:
-------------------------------------

+1

> Move pruned schema tracking logic from LoadFunc to core code
> ------------------------------------------------------------
>
>                 Key: PIG-1330
>                 URL: https://issues.apache.org/jira/browse/PIG-1330
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>    Affects Versions: 0.7.0
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.7.0
>
>         Attachments: PIG-1330-1.patch
>
>
> Currently, LoadFunc.getSchema require a schema after column pruning. The good side of this is LoadFunc.getSchema matches the data it actually load. This gives a sense of consistency. However, by doing this, every LoadFunc need to keep track of the columns pruned. This is an unnecessary burden to the LoadFunc writer and it is very error proning. This issue is to move this logic from LoadFunc to Pig core. LoadFunc.getSchema then only need to return original schema even after pruning.

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