You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Joe McDonnell (JIRA)" <ji...@apache.org> on 2019/08/14 23:21:00 UTC

[jira] [Resolved] (IMPALA-4551) Set limits on size of expression trees

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

Joe McDonnell resolved IMPALA-4551.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.3.0

> Set limits on size of expression trees
> --------------------------------------
>
>                 Key: IMPALA-4551
>                 URL: https://issues.apache.org/jira/browse/IMPALA-4551
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.8.0
>            Reporter: Tim Armstrong
>            Assignee: Joe McDonnell
>            Priority: Major
>             Fix For: Impala 3.3.0
>
>         Attachments: huge_case.patch
>
>
> Very large expression trees can cause havoc in various Impala components. I have been experimenting with the attached test that generates large case statements of varying depths and widths, and have been able to hit limits in the frontend (Java OOM) and caused various runaway memory usage problems in the backend (thrift structures, LLVM IR, codegen, etc).
> We should set some kind of limit here, either on the number of nodes in the expression trees, or on the size of the query text, and then make sure that we can execute queries of the maximum size end-to-end.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org