Return-Path: X-Original-To: apmail-pig-dev-archive@www.apache.org Delivered-To: apmail-pig-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8647918606 for ; Wed, 10 Feb 2016 20:22:18 +0000 (UTC) Received: (qmail 39710 invoked by uid 500); 10 Feb 2016 20:22:18 -0000 Delivered-To: apmail-pig-dev-archive@pig.apache.org Received: (qmail 39659 invoked by uid 500); 10 Feb 2016 20:22:18 -0000 Mailing-List: contact dev-help@pig.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@pig.apache.org Delivered-To: mailing list dev@pig.apache.org Received: (qmail 39642 invoked by uid 500); 10 Feb 2016 20:22:18 -0000 Delivered-To: apmail-hadoop-pig-dev@hadoop.apache.org Received: (qmail 39629 invoked by uid 99); 10 Feb 2016 20:22:18 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 10 Feb 2016 20:22:18 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 15CF52C14F6 for ; Wed, 10 Feb 2016 20:22:18 +0000 (UTC) Date: Wed, 10 Feb 2016 20:22:18 +0000 (UTC) From: "Rohini Palaniswamy (JIRA)" To: pig-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (PIG-4805) Auto-parallelism estimation should use split sub plan specific to the successor MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Rohini Palaniswamy created PIG-4805: --------------------------------------- Summary: Auto-parallelism estimation should use split sub plan specific to the successor Key: PIG-4805 URL: https://issues.apache.org/jira/browse/PIG-4805 Project: Pig Issue Type: Improvement Reporter: Rohini Palaniswamy In PIG-4802, we determine different parallelism factors for different successors (edges). For eg: If we have two successors, one with combine plan and other without we want to compute lesser parallelism factor for the one with the combine plan as that edge will get less data. To be more perfect, we need only look at the split sub-plan that writes to that successor edge. If there is a FILTER in one sub-plan it is accounted for all the successors now which is not right. -- This message was sent by Atlassian JIRA (v6.3.4#6332)