You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Richard Ding (JIRA)" <ji...@apache.org> on 2011/02/16 00:26:57 UTC
[jira] Created: (PIG-1856) Custom jar is not packaged with the new
job created by LimitAdjuster
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
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
[jira] Updated: (PIG-1856) Custom jar is not packaged with the new
job created by LimitAdjuster
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1856:
------------------------------
Attachment: PIG-1856.patch
Test-patch output:
{code}
[exec] +1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] +1 tests included. The patch appears to include 3 new or modified tests.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 release audit. The applied patch does not increase the total number of release audit warnings.
{code}
> 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
[jira] Updated: (PIG-1856) Custom jar is not packaged with the new
job created by LimitAdjuster
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1856:
------------------------------
Status: Patch Available (was: Open)
> 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
[jira] Updated: (PIG-1856) Custom jar is not packaged with the new
job created by LimitAdjuster
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Ding updated PIG-1856:
------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
Patch committed to trunk.
> 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
[jira] Commented: (PIG-1856) Custom jar is not packaged with the
new job created by LimitAdjuster
Posted by "Daniel Dai (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (PIG-1856) Custom jar is not packaged with the
new job created by LimitAdjuster
Posted by "Richard Ding (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996175#comment-12996175 ]
Richard Ding commented on PIG-1856:
-----------------------------------
Unit tests pass.
> 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