You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2011/03/01 20:42:42 UTC

[jira] Commented: (PIG-1856) Custom jar is not packaged with the new job created by LimitAdjuster

    [ https://issues.apache.org/jira/browse/PIG-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13001056#comment-13001056 ] 

Daniel Dai commented on PIG-1856:
---------------------------------

+1

> Custom jar is not packaged with the new job created by LimitAdjuster 
> ---------------------------------------------------------------------
>
>                 Key: PIG-1856
>                 URL: https://issues.apache.org/jira/browse/PIG-1856
>             Project: Pig
>          Issue Type: Bug
>          Components: impl
>    Affects Versions: 0.8.0
>            Reporter: Richard Ding
>            Assignee: Richard Ding
>             Fix For: 0.9.0
>
>         Attachments: PIG-1856.patch
>
>
> The script:
> {code}
> A = load 'data' as (s, m);
> B = order A by s parallel 2;
> C = limit B 20;
> store C into 'output' using org.apache.pig.piggybank.storage.PigStorageSchema('\t')
> {code}
> where piggybank jar is in the classpath.
> The script, however,  fails since the piggybank jar isn't shipped to the backend with the additional job created by the LimitAdjuster.
> The workaround is to explicitly register the piggybank jar in the script. 

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