Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 28 Sep 2016 18:14:20 +0000 (UTC)
From: "Jinfeng Ni (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.13008316.1475084858000.689948.1475086460583@Atlassian.JIRA>
In-Reply-To: <JIRA.13008316.1475084858000@Atlassian.JIRA>
References: <JIRA.13008316.1475084858000@Atlassian.JIRA> <JIRA.13008316.1475084858698@arcas>
Subject: [jira] [Assigned] (DRILL-4911) SimpleParallelizer should avoid plan
 serialization for logging purpose when debug logging is not enabled.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 28 Sep 2016 18:14:22 -0000


     [ https://issues.apache.org/jira/browse/DRILL-4911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinfeng Ni reassigned DRILL-4911:
---------------------------------

    Assignee: Jinfeng Ni

> SimpleParallelizer should avoid plan serialization for logging purpose when debug logging is not enabled.
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: DRILL-4911
>                 URL: https://issues.apache.org/jira/browse/DRILL-4911
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
>            Priority: Minor
>
> SimpleParallelizer and subclass have code to put serialized plan in debug log. However, in case when the physical plan fragment is very large (table is huge with large # of partitions, files, etc), the overhead of serialization is not negligible. The code seems to always do serialization, regardless whether the debug flag is turned on. 
> To reduce the overhead, SimpleParallelizer and subclass should only do plan serialization for logging purpose when debug logging is turned on.


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