Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hama.apache.org
Date: Fri, 28 Sep 2012 12:33:07 +1100 (NCT)
From: "Edward J. Yoon (JIRA)" <jira@apache.org>
To: dev@hama.apache.org
Message-ID: <1729132871.137122.1348795987445.JavaMail.jiratomcat@arcas>
In-Reply-To: <1050018736.114829.1348462447645.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (HAMA-647) Make the  input spliter robustly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Edward J. Yoon commented on HAMA-647:
-------------------------------------

By adding unit tests testComputeGoalSize() and testComputeSplitSize(), you can check whether your formula works for for every case correctly.
                
> Make the  input spliter robustly
> --------------------------------
>
>                 Key: HAMA-647
>                 URL: https://issues.apache.org/jira/browse/HAMA-647
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp core
>    Affects Versions: 0.5.0, 0.6.0
>            Reporter: Yuesheng Hu
>            Assignee: Yuesheng Hu
>            Priority: Critical
>             Fix For: 0.6.0
>
>         Attachments: HAMA-647-2.patch, HAMA-647_3.patch, HAMA-647.patch
>
>
> Currently, the spliter in FileInputFormat is based on the Mapreduce's spliter. But, Hama is different from Mapreduce, Hama's task can not be  pended until the slot becomes free.  So, the current spliter is not suitable for Hama. When input file is small, it may be ok, but when input is  very large, the number of splits will be very large too, even our cluster is powerful enough to handle the input. More details, please see the comments.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira