giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-101) Replace munge with shim layer similar to Pig and Hive
Date Tue, 28 May 2013 17:06:22 GMT

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

Nitay Joffe commented on GIRAPH-101:
------------------------------------

[~maro] thanks for taking this on! You might want to make the whole Hadoop shim layer its
own Java Maven project (i.e. in GitHub or another Apache project) that gets pulled in by Giraph.
There are lots of projects besides Giraph that need Hadoop Shims. Just off the top of my head
the following other projects could benefit from this work: Hive, HBase, HiveIO used by Giraph
itself.
                
> Replace munge with shim layer similar to Pig and Hive
> -----------------------------------------------------
>
>                 Key: GIRAPH-101
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-101
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Avery Ching
>            Assignee: Michael Aro
>              Labels: gsoc, gsoc2013, mentor
>
> Munge (http://sonatype.github.io/munge-maven-plugin/) is a hacky way of support multiple
versions of Hadoop.  The shim layers in Pig and Hive are a cleaner way to do this I think.
> Munge also forces us to release only in source, or to supply different binaries for different
hadoop versions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message