incubator-bigtop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <>
Subject [jira] [Updated] (BIGTOP-570) Build package for Apache Giraph
Date Mon, 21 May 2012 20:20:42 GMT


Andrew Purtell updated BIGTOP-570:

    Attachment: 0001-Giraph-package-WIP.patch.gz

Attached is an updated patch that includes a Giraph smoke test, cribbed from a unit test.
I wish I could report more progress. It took too much time just to figure out Maven was pulling
in dependencies to some defunct repo from ZooKeeper. Now I can't seem to get Maven
to select the correct Hadoop artifact ("java.lang.IncompatibleClassChangeError: Found interface
duce.JobContext, but class was expected
"). Perhaps this is a familiar problem?

Unfortunately just executing 'hadoop jar ...' using iTest Shell is not an option because Giraph
requires execution of more than one task in parallel, something not supported by LocalTaskRunner.
> Build package for Apache Giraph
> -------------------------------
>                 Key: BIGTOP-570
>                 URL:
>             Project: Bigtop
>          Issue Type: New Feature
>            Reporter: Andrew Purtell
>            Assignee: Roman Shaposhnik
>            Priority: Minor
>         Attachments: 0001-Giraph-package-WIP.patch.gz, 0001-Giraph-package-WIP.patch.gz
> We are basing our next internal Hadoop distribution on Bigtop and want to make Apache
Giraph available to our users as part of the platform. Apache Giraph is a promising platform
for running large-scale graph algorithms on top of existing Hadoop infrastructure, currently
in incubation. For more information on the project, please see:
If this is of interest to anyone, I've ported the RPM specfile and common build scripts to
both Bigtop and Giraph trunks. Unfortunately I don't know how to package for Debian.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message