You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pig.apache.org by "Joep Rottinghuis (JIRA)" <ji...@apache.org> on 2011/02/15 00:01:57 UTC
[jira] Created: (PIG-1855) Split hadoop-20.jar into separate
components
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
[jira] Commented: (PIG-1855) Split hadoop-20.jar into separate
components
Posted by "Olga Natkovich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994604#comment-12994604 ]
Olga Natkovich commented on PIG-1855:
-------------------------------------
Starting with Pig 0.8 we actually pickup stuff from maven and no longer use hadoop-app jar.
> 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
[jira] Commented: (PIG-1855) Split hadoop-20.jar into separate
components
Posted by "Joep Rottinghuis (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994622#comment-12994622 ]
Joep Rottinghuis commented on PIG-1855:
---------------------------------------
Would you happen to know off the top of your head if there is a particular patch I can backport, or is that not easily separated from other 0.8 work?
> 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
[jira] Resolved: (PIG-1855) Split hadoop-20.jar into separate
components
Posted by "Olga Natkovich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Olga Natkovich resolved PIG-1855.
---------------------------------
Resolution: Fixed
Please, re-open if this issue requires more attention, thanks
> 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
[jira] Commented: (PIG-1855) Split hadoop-20.jar into separate
components
Posted by "Joep Rottinghuis (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (PIG-1855) Split hadoop-20.jar into separate
components
Posted by "Olga Natkovich (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIG-1855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994915#comment-12994915 ]
Olga Natkovich commented on PIG-1855:
-------------------------------------
not really sure. I would search on Hadoop or maveb keywords in JIRA
> 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