hadoop-pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Francisoud (JIRA)" <j...@apache.org>
Subject [jira] Commented: (PIG-121) NPE in PigContext
Date Wed, 27 Feb 2008 14:31:52 GMT

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

Benjamin Francisoud commented on PIG-121:
-----------------------------------------

This seems to be the same problem as PIG-93: the first stacktrace in my [first comment|https://issues.apache.org/jira/browse/PIG-93?focusedCommentId=12565794#action_12565794]

duplicate ?

> NPE in PigContext
> -----------------
>
>                 Key: PIG-121
>                 URL: https://issues.apache.org/jira/browse/PIG-121
>             Project: Pig
>          Issue Type: Bug
>            Reporter: Stefan Groschupf
>            Priority: Critical
>
> Setting the cluster cause a NPE exception in PigContext in line 214.
> $ java -cp pig.jar org.apache.pig.Main -x mapreduce -c localhost
> Changing MR cluster to localhost
> 08/02/24 20:08:44 ERROR pig.Main: java.lang.NullPointerException
> Main line 109 calls   
> pigContext.setJobtrackerLocation(cluster);
> In line 214 in PigContext executionEngine.updateConfiguration(trackerLocation) is called.
However executionEngine is still null, since connect is not called first. 
> I guess so far people did set cluster and name node as system properties or it was set
by the perl script instead of using the -c parameter. 
> Within the HExecutionEngine#init the system property was used to connect to the hadoop
cluster. 
> Looks like HExecutionEngine, PigContext and PigServer need some refactoring to clean
up those things. 
> I'm happy to offer help here, but I'm not sure if we have enough patch credibility yet.
:-)

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


Mime
View raw message