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

Nigel Savage commented on PIG-3729:
-----------------------------------

thank you very much for your prompt and very helpful response, I was hoping 
that I could find a dependency for the pom that would work, I have searched 
around for a dependency like this for the pig-h2 jar, searching thru this jira 
I think I need something like
  <dependency>
            <groupId>org.apache.pig</groupId>
            <artifactId>pig</artifactId>
            <version>0.12.0</version>
            <classifier>h23</classifier>
  </dependency>
however this does not work
does anyone know the correct for for the maven dependency tag

> 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