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

ChiaHung Lin commented on HAMA-567:
-----------------------------------

My original thought was that we can make use of command pattern (as stated in 
HAMA-503), with which ideally we still can construct flow as usual.For example, 
constructing for loop

For for = new For(conidtion);
for.add(superstepN).add(superstepN1)...;
configurator.add(superstep1).add(superstep2).add(for)...;

... class For implements Comand{
  For(... conditions) { ... }  

  public void execute() {
     for(/* extract from conditions */) { 
        superstep.execute();// extract superstep and then execute
     }
  }
}

With such method, it looks variables can be cross several supersteps. 


                
> BSPPeer should provide means for chaining supersteps to share data among them.
> ------------------------------------------------------------------------------
>
>                 Key: HAMA-567
>                 URL: https://issues.apache.org/jira/browse/HAMA-567
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp core
>    Affects Versions: 0.6.0
>            Reporter: Suraj Menon
>             Fix For: 0.6.0
>
>         Attachments: Mapper.java
>
>
> In most scenarios, a superstep would need certain values or objects that were 
> computed in the previous superstep. When using the chaining Superstep design 
> to implement BSP algorithms, this gets a little ugly/difficult to implement. 
> BSPPeer should provide means (preferably a map<String,Object>) so that the 
> next Superstep can ask for the values in previous superstep using String 
> token to query the map. Also, this map could be checkpointed periodically in 
> the background so that we can completely recover the state of a task after 
> failure. The BSPPeer object should have a dedicated get and set function for 
> updating values in the peer.

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

        

Reply via email to