incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HAMA-332) Renaming some members in BSPMaster to follow the Hama terminology (and be less "Hadoopish")
Date Mon, 22 Nov 2010 00:57:13 GMT

     [ https://issues.apache.org/jira/browse/HAMA-332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Edward J. Yoon resolved HAMA-332.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

Thanks! Filipe. I'v just committed this.

Sorry for my late commit. I was busy all through the week. :)



> Renaming some members in BSPMaster to follow the Hama terminology (and be less "Hadoopish")
> -------------------------------------------------------------------------------------------
>
>                 Key: HAMA-332
>                 URL: https://issues.apache.org/jira/browse/HAMA-332
>             Project: Hama
>          Issue Type: Improvement
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>            Priority: Trivial
>             Fix For: 0.2.0
>
>         Attachments: HAMA-332.patch
>
>
> While doing a code walk in order to implement the job kill feature, I found out we have
a few map members in BSPMaster.java that are too closed with the Hadoop MapReduce terminology.
Namely, the names refer to "trackers", which in Hama are "groom servers".
> The following path just renames these members to be more closely tied to the Hama terminology.
> I also moved those attributes to the top of the class definition (close to all the other
attributes).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message