[jira] Updated: (PIG-1717) pig needs to call setPartitionFilter if schema is null but getPartitionKeys is not

["Gerrit Jansen van Vuuren (JIRA)" <ji...@apache.org>]

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

Gerrit Jansen van Vuuren updated PIG-1717:
------------------------------------------

    Attachment: PIG-1717.v2.patch

> pig needs to call setPartitionFilter if schema is null but getPartitionKeys is not
> ----------------------------------------------------------------------------------
>
>                 Key: PIG-1717
>                 URL: https://issues.apache.org/jira/browse/PIG-1717
>             Project: Pig
>          Issue Type: Improvement
>          Components: impl
>    Affects Versions: 0.9.0
>            Reporter: Gerrit Jansen van Vuuren
>            Assignee: Gerrit Jansen van Vuuren
>            Priority: Minor
>             Fix For: 0.9.0
>
>         Attachments: PIG-1717.patch, PIG-1717.v1.patch, PIG-1717.v2.patch, patchReleaseAuditWarnings.txt.gz, testlog.tgz, trunkReleaseAuditWarnings.txt.gz
>
>
> I'm writing a loader that works with hive style partitioning e.g. /logs/type1/daydate=2010-11-01
> The loader does not know the schema upfront and this is something that the user adds in the script using the AS clause.
> The problem is that this user defined schema is not available to the loader, so the loader cannot return any schema, the Loader does know what the partition keys are and pig needs in some way to know about these partition keys. 
> Currently if the schema is null pig never calls the LoadMetaData:getPartitionKeys method or the setPartitionFilter method.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira