incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (Issue Comment Edited) (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (HAMA-439) Reorganize modules for YARN/MR-NextGen integration
Date Tue, 27 Sep 2011 11:41:12 GMT

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

Edward J. Yoon edited comment on HAMA-439 at 9/27/11 11:41 AM:
---------------------------------------------------------------

Yes, I have a bunch of meetings in this week. So I can work on this this weekend.

But here's my quick comments,

As we discussed above, let's commit to the trunk repository directly. We can upload the patches
for review. 

P.S., Please use the svn copy command if you want to create a branch.

{quote}
-I've transfered all modules, there is no source movement yet.
{quote}

I think, {code}*Message.class, BSP.class, BSPInterface.class, and BSPMessage*.class{code}
should be moved into 'api/src/main/java/org/apache/hama/bsp'.

And Job submission related classes should be moved into 'client/src/main/java/org/apache/hama/bsp'.

Other classes are all the Hama classic-server stuffs.
                
      was (Author: udanax):
    Yes, I have a bunch of meetings in this week. So I can work on this this weekend.

But here's my quick comments,

As we discussed above, let's commit to the trunk repository directly. We can upload the patches
for review. 

P.S., Please use the svn copy command if you want to create a branch.

{quote}
-I've transfered all modules, there is no source movement yet.
{quote}

I think, *Message.class, BSP.class, BSPInterface.class, and BSPMessage*.class should be moved
into 'api/src/main/java/org/apache/hama/bsp'.

And Job submission related classes should be moved into 'client/src/main/java/org/apache/hama/bsp'.

Other classes are all the Hama classic-server stuffs.
                  
> Reorganize modules for YARN/MR-NextGen integration
> --------------------------------------------------
>
>                 Key: HAMA-439
>                 URL: https://issues.apache.org/jira/browse/HAMA-439
>             Project: Hama
>          Issue Type: Sub-task
>    Affects Versions: 0.3.0
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Thomas Jungblut
>             Fix For: 0.4.0
>
>
> I'd like to get started on HamaV2 to work with YARN/MR-nextgen.
> Here's what I think should be the module structure:
>  - *api*: Code from HamaV1 related to APIs that will be moved to this new module. This
will mainly have the BSP APIs: _BSP_, _BSPPeerInterface_ and all the related records like
_BSPMessage_, _BSPMessageBundle etc.
>  - *core*: Current/HamaV1 server code. Will have the current _BSPMaster_/_GroomServer_
infrastructure. We should probably rename it to {{classic-server}} or something similar.
>  - *server*: New Hama server implementation to work with YARN. Will have _BSPApplicationMaster_,
_BSPTask_ and related code.
>  - *client*: Code from HamaV1 related to client that will be moved to this new module.
This will mainly have the client-submission classes/interfaces like _BSPJob_, _BSPJobClient_,
_JobStatus_ etc. It will be configurable to either run with the classic-server implementation
or with YARN.
> There will not be any package changes but only code-moves across modules, so we will
be backwards compatible.
> How does it look? Any thoughts/suggestions?

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