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

Riza Suminto updated IMPALA-14519:
----------------------------------
    Description: 
The following query should select only id column and skip materializing any 
complex columns that is not in the select list.
{code:java}
WITH view1 AS (
SELECT
  id,
  struct1.f1 as s1f1,
  struct1.f2 as s1f2,
  struct2.value.f1 as s2f1,
  struct2.value.f2 as s2f2
FROM
  functional.allcomplextypes,
  functional.allcomplextypes.struct_array_col struct1,
  functional.allcomplextypes.struct_map_col struct2
)
SELECT id FROM view1;{code}
Currently, all complex columns listed in the view are materialized within 
SUBPLAN, as seen in the attached query profile.

  was:
The following query should select only id column and skip materializing any 
complex columns that is not in the select list.
{code:java}
WITH view1 AS (  
SELECT
  id,
  struct1.f1 as s1f1,
  struct1.f2 as s1f2,
  struct2.f1 as s2f1,
  struct2.f2 as s2f2
FROM
  functional.allcomplextypes,
  functional.allcomplextypes.struct_array_col struct1,
  functional.allcomplextypes.struct_map_col,
  functional.allcomplextypes.struct_map_col struct2
)
SELECT id FROM view1; {code}
Currently, all complex columns listed in the view are materialized within 
SUBPLAN, as seen in the attached query profile.


> Complex type columns should not materialize if it is not in select list
> -----------------------------------------------------------------------
>
>                 Key: IMPALA-14519
>                 URL: https://issues.apache.org/jira/browse/IMPALA-14519
>             Project: IMPALA
>          Issue Type: Improvement
>          Components: Frontend
>            Reporter: Riza Suminto
>            Priority: Major
>         Attachments: profile_7943ee11b3118a13_fdba1a6700000000.txt
>
>
> The following query should select only id column and skip materializing any 
> complex columns that is not in the select list.
> {code:java}
> WITH view1 AS (
> SELECT
>   id,
>   struct1.f1 as s1f1,
>   struct1.f2 as s1f2,
>   struct2.value.f1 as s2f1,
>   struct2.value.f2 as s2f2
> FROM
>   functional.allcomplextypes,
>   functional.allcomplextypes.struct_array_col struct1,
>   functional.allcomplextypes.struct_map_col struct2
> )
> SELECT id FROM view1;{code}
> Currently, all complex columns listed in the view are materialized within 
> SUBPLAN, as seen in the attached query profile.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to