Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-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 8E45617FC5 for ; Tue, 30 Sep 2014 02:36:34 +0000 (UTC) Received: (qmail 91261 invoked by uid 500); 30 Sep 2014 02:36:34 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 91192 invoked by uid 500); 30 Sep 2014 02:36:34 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 91181 invoked by uid 500); 30 Sep 2014 02:36:34 -0000 Delivered-To: apmail-hadoop-hive-dev@hadoop.apache.org Received: (qmail 91178 invoked by uid 99); 30 Sep 2014 02:36:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Sep 2014 02:36:34 +0000 Date: Tue, 30 Sep 2014 02:36:34 +0000 (UTC) From: "Xuefu Zhang (JIRA)" To: hive-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HIVE-8278) Restoring a graph representation of SparkPlan [Spark Branch] 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/HIVE-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14152731#comment-14152731 ] Xuefu Zhang commented on HIVE-8278: ----------------------------------- +1 > Restoring a graph representation of SparkPlan [Spark Branch] > ------------------------------------------------------------ > > Key: HIVE-8278 > URL: https://issues.apache.org/jira/browse/HIVE-8278 > Project: Hive > Issue Type: Sub-task > Components: Spark > Reporter: Chao > Assignee: Chao > Attachments: HIVE-8278.1-spark.patch, HIVE-8278.2-spark.patch, HIVE-8278.3-spark.patch > > > HIVE-8249 greatly simply file the SparkPlan model and the SparkPlanGenerator logic. As a side effect, however, a visual representation of SparkPlan got lost. Such representation is helpful for debugging and performance profiling. In addition, it would be also good to separate plan generation and plan execution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)