[IMPALA-2492] CTAS with nested type path expression in select list fails

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: Impala 2.3.0
• Labels: nested_types planner
• Target Version: Impala 2.5.0
• Assignee: Unassigned
• Reporter: Matthew Jacobs
• Created: 07/Oct/15 00:42
• Updated: 07/Oct/15 00:45
• Resolved: 07/Oct/15 00:45

Description

A CTAS with a nested type path expression in the select list fails analysis though the SELECT expression executes fine if it's not used in a CREATE TABLE statement.

Query: create table test2 as select t1.field_102.field_104.field_107
FROM table_3 t1
INNER JOIN t1.field_86 t2
INNER JOIN t1.field_102.field_104.field_108.field_110 t3
INNER JOIN table_5 t4
WHERE
NOT EXISTS (SELECT
tt1.pos  AS int_col
FROM t1.field_102.field_104.field_108.field_110 tt1
CROSS JOIN t1.field_86 tt2
WHERE
((tt1.pos) IN (tt1.pos, -581.8)) AND (((t1.field_85) = (tt2.key)) AND ((t1.field_82) = (tt2.value.field_94))))
ERROR: AnalysisException: Invalid column/field name: field_102.field_104.field_107