[
https://issues.apache.org/jira/browse/PIG-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994547#comment-12994547
]
Joep Rottinghuis commented on PIG-1855:
---------------------------------------
One reason why one would want to copile Hive against own Hadoop build is when
the shipped version of Hadoop in Pig is incompatible with the version of Hadoop
one runs. An example of that would be Hadoop 0.20.100 (see HADOOP-7108).
Will have to ask the developer who reported this what the exact output was...
> Split hadoop-20.jar into separate components
> --------------------------------------------
>
> Key: PIG-1855
> URL: https://issues.apache.org/jira/browse/PIG-1855
> Project: Pig
> Issue Type: Improvement
> Reporter: Joep Rottinghuis
>
> Currently Pig compiles against a pre-packaged, source controlled set of
> versions of Hadoop:
> lib/hadoop18.jar and lib/hadoop20.jar.
> While this is convenient for Pig development as a standalone activity it
> makes it a pain to be able to use:
> 1) The hadoop??.jar contains classes that do not belong to the o.a.h
> namespace. In other words it contains com.sun.*, org.apache.jasper and all
> sorts of other auxiliary classes used by hadoop.
> 2) When building Pig against your own version of Hadoop one has to untar the
> hadoop20.jar, splice in the o.a.h classes, re-pack (and commit to source
> control?)
> One would expect the ability to be able to point Pig build to output from own
> Hadoop build.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
