You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (Commented) (JIRA)" <ji...@apache.org> on 2012/01/04 09:45:38 UTC
[jira] [Commented] (HAMA-476) Splitter doesn't work correctly
[ https://issues.apache.org/jira/browse/HAMA-476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13179347#comment-13179347 ]
Thomas Jungblut commented on HAMA-476:
--------------------------------------
Cool feature, but I guess we have to repartion the dataset to maxtask and add log warnings
> Splitter doesn't work correctly
> -------------------------------
>
> Key: HAMA-476
> URL: https://issues.apache.org/jira/browse/HAMA-476
> Project: Hama
> Issue Type: Bug
> Components: bsp
> Affects Versions: 0.3.0
> Reporter: Edward J. Yoon
> Assignee: Edward J. Yoon
> Fix For: 0.4.0
>
> Attachments: patch_01.txt
>
>
> - To split sequencefile as user requested size, there's no way to avoid read/write records. I think we have to use just blockSize.
> - Unlike MapReduce, we are unable to queuing tasks when exceeds cluster capacity (I have no idea at the moment).
--
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