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

Ashlee Lee commented on PIG-3729:
---------------------------------

Different situation for me. I tried both pig-0.12.0.jar in mvnrepository and my 
recomplied pig jar, but when I run my jar which use PigServer to run 
pigscripts, it failed with ERROR 4010: Cannot find hadoop configurations in 
classpath (neither hadoop-site.xml nor core-site.xml was found in the 
classpath). I have PIG_CLASS_PATH and HADOOP_CONF_DIR setted. 

Then I tried above h2 version dependency, it comes 
error>java.lang.NoClassDefFoundError: org/apache/pig/PigServer.

My jar is working fine with Pig 0.11.0 and Hadoop 1.2.0, but now I want to run 
in Pig 0.12.0 and Hadoop 2.2.0.......I need help!

> Need to rebuild pig 0.12.0 jar from mvnrepository.com to resove error in 
> hadoop 2.2 0 
> --------------------------------------------------------------------------------------
>
>                 Key: PIG-3729
>                 URL: https://issues.apache.org/jira/browse/PIG-3729
>             Project: Pig
>          Issue Type: Bug
>          Components: build, internal-udfs
>    Affects Versions: 0.12.0
>         Environment: debian single node pseudo distributed hadoop 2.2 cluster
>            Reporter: Nigel Savage
>            Priority: Blocker
>              Labels: Hadoop, Iteator, Pig, PigServer
>
> Unable to get pig 0.12.0 to run single node pseudo distributed hadoop 2.2 
> cluster using the jar from mvnrepository.com 
> this is the error
> "org.apache.pig.impl.logicalLayer.FrontendException: ERROR 1066: Unable to 
> open iterator for alias"
> if I download the jar from
> http://apache.claz.org/pig/pig-0.12.0/pig-0.12.0.tar.gz  
> and then recompile the src with  "ant clean jar -Dhadoopversion=23"  
> when I install the recompiled  jar in .m2 everything works
> If it is the case that the Apache hadoop 2.2.0 jars are backwardly compatible 
> then could some one comment on what could be the issue?



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to