incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-431) MapReduce NG integration
Date Tue, 11 Oct 2011 14:17:12 GMT

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

Thomas Jungblut commented on HAMA-431:
--------------------------------------

Putting Avro into CP worked fine.
But I'm facing relative huge issues with our project now.

In every of our module, we have hadoop-20.2 as dependency.
SERVER module is depending on API and CORE, now hadoop-20.2 ships within every jar export
/ snapshot build. Old classes override the new ones during the build process.

Should I change the hadoop 20.2 dependency to 23.0 in every module to fix this? I see several
compatibility issues in our main packages, especially with Zookeeper. 

I'm still thinking about just making the whole module depending on a Hama-0.4.0 SNAPSHOT and
develop further. The integration totally sucks.
                
> MapReduce NG integration
> ------------------------
>
>                 Key: HAMA-431
>                 URL: https://issues.apache.org/jira/browse/HAMA-431
>             Project: Hama
>          Issue Type: New Feature
>            Reporter: Thomas Jungblut
>            Assignee: Thomas Jungblut
>         Attachments: job_state.dot, task_phase.dot, task_state.dot
>
>
> We should take a look at how to integrate Hama's BSP Engine to Hadoop's nextGen application
platform.
> Can be currently found in the 0.23 branch.

--
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

        

Mime
View raw message