You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Tim Armstrong (JIRA)" <ji...@apache.org> on 2018/04/30 16:22:00 UTC

[jira] [Resolved] (IMPALA-6560) Come up with reliable regression test for IMPALA-2376

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

Tim Armstrong resolved IMPALA-6560.
-----------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0
                   Impala 2.13.0

> Come up with reliable regression test for IMPALA-2376
> -----------------------------------------------------
>
>                 Key: IMPALA-6560
>                 URL: https://issues.apache.org/jira/browse/IMPALA-6560
>             Project: IMPALA
>          Issue Type: Test
>          Components: Backend
>            Reporter: Tim Armstrong
>            Assignee: Tim Armstrong
>            Priority: Major
>              Labels: resource-management
>             Fix For: Impala 2.13.0, Impala 3.1.0
>
>
> We don't have a good regression test for IMPALA-2376. With IMPALA-4835 and other changes it's increasingly difficult to get the query to OOM at the intended place. We probably need to construct some special test data with a very large nested collection to trigger this bug.
> This is based on the TODO:
> {noformat}
> ====
> ---- QUERY
> # IMPALA-2376
> # Set memory limit low enough to get the below query to consistently fail.
> # TODO: change query and/or table so we can consistently check for the following error:
> # Failed to allocate buffer for collection '...'.
> set mem_limit=4m;
> select max(cnt) from customer c,
> (select count(l_returnflag) cnt from c.c_orders.o_lineitems) v;
> ---- TYPES
> BIGINT
> ---- CATCH
> Memory limit exceeded
> {noformat}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)