drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5290) Provide an option to build operator table once for built-in static functions and reuse it across queries.
Date Fri, 24 Feb 2017 01:39:44 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15881747#comment-15881747

ASF GitHub Bot commented on DRILL-5290:

Github user paul-rogers commented on a diff in the pull request:

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/ExecConstants.java ---
    @@ -413,4 +413,8 @@
       String DYNAMIC_UDF_SUPPORT_ENABLED = "exec.udf.enable_dynamic_support";
true, true);
    +  String USE_DYNAMIC_UDFS_KEY = "exec.udf.use_dynamic";
    --- End diff --
    ENABLE_DYNAMIC_UDF and exec.udf.enable_dynamic?

> 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: Improvement
>    Affects Versions: 1.9.0
>            Reporter: Padma Penumarthy
>            Assignee: Padma Penumarthy
>              Labels: doc-impacting
>             Fix For: 1.10.0
> 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, 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 a system/session option to not use dynamic UDFs so we can use the operator table
saved in DrillbitContext and avoid building each time.
> *Please note, changes are adding new option exec.udf.use_dynamic which needs to be documented.*

This message was sent by Atlassian JIRA

View raw message