[
https://issues.apache.org/jira/browse/HAMA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13119429#comment-13119429
]
Thomas Jungblut commented on HAMA-439:
--------------------------------------
That is fine.
But I guess if we stick with patches for the current trunk development, it
won't be a problem to merge it together. I'm trying to keep the modules in the
branch consistent to the trunk.
I know that I'm going to have a lot of pain anyways ;D
> 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
>
> Attachments: HAMA-349-20110927.txt, HAMA-349-move-20110927.sh,
> HAMA-349-move_v2.patch, HAMA-349-move_v2.sh, HAMA-349-move_v3.patch,
> HAMA-349-move_v4.patch, HAMA-349-move_v4.sh, HAMA-349-move_v5.patch,
> HAMA-439.patch
>
>
> 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
