You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Olga Natkovich (JIRA)" <ji...@apache.org> on 2010/07/12 21:41:50 UTC

[jira] Updated: (PIG-932) Required fields projection in Loader: nested fields in bag/tuple, map key lookup more than two levels

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

Olga Natkovich updated PIG-932:
-------------------------------

    Assignee: Daniel Dai

Possible work for 0.8.0. Need to see if we have time

> Required fields projection in Loader: nested fields in bag/tuple, map key lookup more than two levels
> -----------------------------------------------------------------------------------------------------
>
>                 Key: PIG-932
>                 URL: https://issues.apache.org/jira/browse/PIG-932
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>    Affects Versions: 0.3.0
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.8.0
>
>
> To leverage the performance features provided by Zebra, Pig should be able to figure out which input fields are actually used in Pig script, and prune unnecessary inputs. This feature is being implementing in [PIG-922|https://issues.apache.org/jira/browse/PIG-922]. However, there are two limitations currently:
> 1. Pruning nested fields only apply to map. We do not prune sub-field inside a bag or tuple
> 2. For map, currently we only go one level deep. Eg, if in Pig script, user uses a#'key0'#'key1', a#'key0' will be asked
> These two limitations are in line with current limitation of Zebra loader. Once Zebra loader can handle this, we need to work to lift these limitations.

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