[
https://issues.apache.org/jira/browse/HAMA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Jungblut updated HAMA-439:
---------------------------------
Attachment: HAMA-439.patch
I'm going to make patches for this, so you can review it.
I've managed to get the module dependencies running, it is not as beautiful as
I would like to have it, but we can refactor it later.
I observed another thing: we have an inconsistency with our BSP and
BSPPeer/Interface.
If we move BSP/BSPInterface to API module, there is no BSPPeer class which is
needed for the parameter. But we have an interface for it called
BSPPeerInterface.
I think this naming is not good, we should name the interface "BSPPeer" and the
implementation "BSPPeerImpl".
This way we don't need to rewrite the examples, just rename it in our code.
This patch will reflect this. I'm sorry for the code change, but this is an
inconsistency we did not see until now.
Unit tests and mvn install are still running fine.
The client module is a TODO, it is quite coupled. I'm not sure if we should
make a module for it.
> 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-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
