giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Akila Wajirasena (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-101) Replace munge with shim layer similar to Pig and Hive
Date Mon, 23 Jun 2014 05:54:25 GMT

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

Akila Wajirasena commented on GIRAPH-101:
-----------------------------------------

I successfully implemented shim loader class similar to hive for girpah. Now I'm trying to
move the munge codes to use the shim layer. I moved ImmutableOutputCommitter successfully.

The problem that I have is, all of these classes are in the girpah-core module and it might
not makes sense moving some of these to the shim module. But, since giraph-core depends on
the shim module there is no other way to do it. 
In addition there are some interfaces like giraph-core/src/main/java/org/apache/giraph/comm/WorkerClient.java
too. 

What do you think is the best thing to do?

> 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 was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message