You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/09/04 01:30:52 UTC

[jira] [Updated] (MAPREDUCE-5569) FloatSplitter is not generating correct splits

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

Allen Wittenauer updated MAPREDUCE-5569:
----------------------------------------
    Fix Version/s:     (was: 3.0.0)

> FloatSplitter is not generating correct splits
> ----------------------------------------------
>
>                 Key: MAPREDUCE-5569
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5569
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>    Affects Versions: trunk, 2.1.0-beta, 1.3.0, 0.23.9
>            Reporter: Nathan Roberts
>            Assignee: Nathan Roberts
>             Fix For: 1.3.0, 0.23.10, 2.3.0
>
>         Attachments: MAPREDUCE-5569-branch-1.patch, MAPREDUCE-5569-trunk.patch
>
>
> The closing split is not calculated correctly:
> {code}
>      // Catch any overage and create the closed interval for the last split.
>      if (curLower <= maxVal || splits.size() == 1) {
>        splits.add(new DataDrivenDBInputFormat.DataDrivenDBInputSplit(
> -          lowClausePrefix + Double.toString(curUpper),
> +          lowClausePrefix + Double.toString(curLower),
>            colName + " <= " + Double.toString(maxVal)));
>      }
> {code}
> For the case of min=5.0, max=7.0, 2 splits, the current code returns splits of (column1 >=5.0, column1 <6.0), (column1 >=7.0, column1 <=7.0). The second split is obviously not correct.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)