Mailing-List: contact issues-help@tez.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@tez.incubator.apache.org
Date: Tue, 27 Aug 2013 16:47:52 +0000 (UTC)
From: "Rohini Palaniswamy (JIRA)" <jira@apache.org>
To: issues@tez.incubator.apache.org
Message-ID: <JIRA.12665294.1377284372026.40193.1377622072336@arcas>
In-Reply-To: <JIRA.12665294.1377284372026@arcas>
References: <JIRA.12665294.1377284372026@arcas>
Subject: [jira] [Commented] (TEZ-393) Handle custom partitioners
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rohini Palaniswamy commented on TEZ-393:
----------------------------------------

bq. The decision to enable or disable dynamic reduce concurrency will be set by the user. So the user can choose to not use it.
  That is good. Most of our hbase users are writing custom partitioners for pig to partition data based on their region server partitions. Will this disabling option be per vertex as we will want to turn it off only for those stages of the DAG where the customer partitioner is applied?  
                
> Handle custom partitioners
> --------------------------
>
>                 Key: TEZ-393
>                 URL: https://issues.apache.org/jira/browse/TEZ-393
>             Project: Apache Tez
>          Issue Type: Sub-task
>            Reporter: Rohini Palaniswamy
>
>   With dynamic allocation of reducers, cases like range partitioning (for ORDER BY) need to be handled properly. Also many users have other custom partitioners. So might be good to have an option to turn of dynamic reducer allocation in case they don't work well with dynamic allocation. 

--
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