[
https://issues.apache.org/jira/browse/HAMA-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13112344#comment-13112344
]
Vinod Kumar Vavilapalli commented on HAMA-439:
----------------------------------------------
bq. Would it better to apply this using git? It seems that git is good at
managing such issues (branching, merging, etc.), and hama has its own git repos
http://git.apache.org/hama.git(?)
Apache repositories on git are read-only. I'd love to get this done on git, but
apache repos only are supported on svn.
bq. I don't know how fast Vinod is, but I'm a hacker, so we are going to finish
this long time before the end of the year ;D
Sure, I am neck deep in core YARN, will try to invest in as many cycles as
possible here.
Thanks Ed for taking this up. If you can't find time for this till weekend, I
can quickly do this. I already did much larger moves in hadoop mapreduce for
the sake of YARN :)
> 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: Edward J. Yoon
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
