tez-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bikas Saha (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (TEZ-1656) Grouping of splits should maintain the original ordering of splits within a group
Date Tue, 21 Oct 2014 20:28:34 GMT

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

Bikas Saha edited comment on TEZ-1656 at 10/21/14 8:28 PM:
-----------------------------------------------------------

Will leave the SplitHolder for TEZ-1692. I think we can use that to refactor and remove the
duplication. After that it will be easier to use that instead of original splits.

Renamed to repeatable. Not sure why it should be unstable. I dont think the repeatability
guarantee will change over time.

Thanks for the review.


was (Author: bikassaha):
Will leave the SplitHolder for TEZ-1692. I think we can use that to refactor and remove the
duplication. After that it will be easier to use that instead of original splits.

Renamed to repeatable. Not sure why it should be unstable. I dont think the repeatability
guarantee will change over time.

> Grouping of splits should maintain the original ordering of splits within a group
> ---------------------------------------------------------------------------------
>
>                 Key: TEZ-1656
>                 URL: https://issues.apache.org/jira/browse/TEZ-1656
>             Project: Apache Tez
>          Issue Type: Task
>            Reporter: Bikas Saha
>            Assignee: Bikas Saha
>         Attachments: TEZ-1656.1.patch, TEZ-1656.2.patch, TEZ-1656.3.patch
>
>
> Sometimes the original splits may have an ordering (eg. splits from a sorted file). Maintaining
the ordering of splits inside a group maintains the sort order.
> The node level grouping maintains ordering. When collecting leftover groups for rack
level grouping, the ordering is lost in current code.



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

Mime
View raw message