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

Daniel Dai commented on PIG-3892:
---------------------------------

bq. Whether hadoop1 or hadoop2, HADOOP_CORE_JAR is not zero-length, so the 
following doesn't work
How do you install Hadoop 2? I download Apache tar ball and it does not contain 
hadoop-core.jar. Is there an easy way to distinguish h2 from h1 from your 
installation?
bq. jar-all-h12 shouldn't depend on jar and jar-withouthadoop
It should not, new patch will remove this
bq.Won't this break BigTop for the same reason as PIG-3905 because ivy will 
resolve both hadoop1 and hadoop2 dependencies no matter what the value of 
hadoopversion is? 
Yes, "ant package" will create the distribution layout containing both 
pig-h1.jar and pig-h2.jar, which will need both hadoop 1 and hadoop 2 
dependency. It might create some trouble if the private maven repository only 
carry h2 build artifacts. But can BIGTOP specify public maven repository as an 
alternative? [~gkesavan], [~cos], want to comment on this?

> Pig distribution for hadoop 2
> -----------------------------
>
>                 Key: PIG-3892
>                 URL: https://issues.apache.org/jira/browse/PIG-3892
>             Project: Pig
>          Issue Type: Bug
>          Components: build
>            Reporter: Daniel Dai
>            Assignee: Daniel Dai
>             Fix For: 0.13.0
>
>         Attachments: PIG-3892-1.patch, PIG-3892-2.patch
>
>
> Currently Pig distribution only bundle pig.jar for Hadoop 1. For Hadoop 2 
> users they need to compile again using -Dhadoopversion=23 flag. That is a 
> quite confusing process. We need to make Pig work with Hadoop 2 out of box. I 
> am thinking two approaches:
> 1. Bundle both pig-h1.jar and pig-h2.jar in distribution, and bin/pig will 
> chose the right pig.jar to run
> 2. Make two Pig distributions for Hadoop 1 and Hadoop 
> Any opinion?



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to