Return-Path: X-Original-To: apmail-tez-issues-archive@minotaur.apache.org Delivered-To: apmail-tez-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D7E0A17995 for ; Tue, 21 Oct 2014 20:28:34 +0000 (UTC) Received: (qmail 49791 invoked by uid 500); 21 Oct 2014 20:28:34 -0000 Delivered-To: apmail-tez-issues-archive@tez.apache.org Received: (qmail 49739 invoked by uid 500); 21 Oct 2014 20:28:34 -0000 Mailing-List: contact issues-help@tez.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@tez.apache.org Delivered-To: mailing list issues@tez.apache.org Received: (qmail 49729 invoked by uid 99); 21 Oct 2014 20:28:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 20:28:34 +0000 Date: Tue, 21 Oct 2014 20:28:34 +0000 (UTC) From: "Bikas Saha (JIRA)" To: issues@tez.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (TEZ-1656) Grouping of splits should maintain the original ordering of splits within a group MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)