You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Thejas M Nair (JIRA)" <ji...@apache.org> on 2010/07/24 01:17:50 UTC

[jira] Commented: (PIG-1489) Pig MapReduceLauncher does not use jars in register statement

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

Thejas M Nair commented on PIG-1489:
------------------------------------

+1 
You can commit after verifying that tests & checks are passing.


>  Pig MapReduceLauncher does not use jars in register statement 
> ---------------------------------------------------------------
>
>                 Key: PIG-1489
>                 URL: https://issues.apache.org/jira/browse/PIG-1489
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Olga Natkovich
>            Assignee: Richard Ding
>             Fix For: 0.8.0
>
>         Attachments: PIG-1489.patch, PIG-1489.patch, PIG-1489_1.patch
>
>
> If my Pig StorFunc has its own OutputFormat class then Pig MapReducelauncher will try to instantiate it before
> launching the mapreduce job and fail with ClassNotFoundException.
> This happens because Pig MapReduce launcher uses its own classloader and ignores the classes in the jars in the
> register statement.
> The effect is that the jars not only have to be in "register " statement in the script but also in the pig
> classpath with the -classpath tag. 
> This can be remedied by making the Pig MapReduceLauncher constructing a classloader that includes the registered jars
> and using that to instantiate the OutputFormat class.

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