Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Wed, 22 Feb 2017 18:51:44 +0000 (UTC)
From: "Padma Penumarthy (JIRA)" <jira@apache.org>
To: dev@drill.apache.org
Message-ID: <JIRA.13045334.1487789479000.34120.1487789504060@Atlassian.JIRA>
In-Reply-To: <JIRA.13045334.1487789479000@Atlassian.JIRA>
References: <JIRA.13045334.1487789479000@Atlassian.JIRA> <JIRA.13045334.1487789479569@jira-lw-us.apache.org>
Subject: [jira] [Created] (DRILL-5290) Provide an option to build operator
 table once for built-in static functions and reuse it across queries.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Feb 2017 18:51:48 -0000

Padma Penumarthy created DRILL-5290:
---------------------------------------

             Summary: Provide an option to build operator table once for built-in static functions and reuse it across queries.
                 Key: DRILL-5290
                 URL: https://issues.apache.org/jira/browse/DRILL-5290
             Project: Apache Drill
          Issue Type: Bug
    Affects Versions: 1.9.0
            Reporter: Padma Penumarthy
            Assignee: Padma Penumarthy
             Fix For: 1.10


Currently, DrillOperatorTable which contains standard SQL operators and functions and Drill User Defined Functions (UDFs) (built-in and dynamic) gets built for each query as part of creating QueryContext. This is an expensive operation ( ~30 msec to build) and allocates  ~2M on heap for each query. For high throughput, concurrent low latency operational queries, we quickly run out of heap memory, causing JVM hangs. Build operator table once during startup for static built-in functions and save in DrillbitContext, so we can reuse it across queries.
Provide an system/session option to not use dynamic UDFs so we can use the operator table saved in DrillbitContext and avoid building each time.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)