pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PIG-2388) Make shim for Hadoop 0.20 and 0.23 support dynamic
Date Thu, 01 Dec 2011 20:12:41 GMT

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

Thomas Weise commented on PIG-2388:

We are going to solve this through our internal build/packaging process based on the current
support. For external distributions, perhaps it makes sense to just offer separate packages
per Hadoop versions rather than trying to make a single package that has this added complexity
embedded? I assume other projects (Hive etc.) are going to have the same problem.

> Make shim for Hadoop 0.20 and 0.23 support dynamic
> --------------------------------------------------
>                 Key: PIG-2388
>                 URL: https://issues.apache.org/jira/browse/PIG-2388
>             Project: Pig
>          Issue Type: Improvement
>    Affects Versions: 0.10, 0.9.2
>            Reporter: Thomas Weise
>            Assignee: Thomas Weise
>             Fix For: 0.10, 0.9.2
>         Attachments: PIG-2388_branch-0.9.patch
> We need a single Pig installation that works with both Hadoop versions. The current shim
implementation assumes different builds for each version. We can solve this statically through
internal build/installation system or by making the shim dynamic so that pig.jar will work
on both version with runtime detection. Attached patch is to convert the static shims into
a shim interface with 2 implementations, each of which will be compiled against the respective
Hadoop version and included into single pig.jar (similar to what Hive does).
> The default build behavior remains unchanged, only the shim for ${hadoopversion} will
be compiled. Both shims can be built via:  ant -Dbuild-all-shims=true

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message