[ 
https://issues.apache.org/jira/browse/HIVE-24664?focusedWorklogId=541278&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-541278
 ]

ASF GitHub Bot logged work on HIVE-24664:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jan/21 20:05
            Start Date: 25/Jan/21 20:05
    Worklog Time Spent: 10m 
      Work Description: jcamachor commented on a change in pull request #1892:
URL: https://github.com/apache/hive/pull/1892#discussion_r564004991



##########
File path: 
itests/hive-blobstore/src/test/results/clientpositive/insert_into_dynamic_partitions.q.out
##########
@@ -100,7 +100,7 @@ STAGE PLANS:
             Statistics: Num rows: 1 Data size: 10 Basic stats: COMPLETE Column 
stats: COMPLETE
             GatherStats: false
             Select Operator
-              expressions: array(const struct(1,'101'),const 
struct(2,'202'),const struct(3,'303'),const struct(4,'404'),const 
struct(5,'505')) (type: array<struct<col1:int,col2:string>>)
+              expressions: 
array(named_struct('col1',1,'col2','101'),named_struct('col1',2,'col2','202'),named_struct('col1',3,'col2','303'),named_struct('col1',4,'col2','404'),named_struct('col1',5,'col2','505'))
 (type: array<struct<col1:int,col2:string>>)

Review comment:
       This should not change, i.e., it seems we are failing to recognize 
constant structs now. Iirc this is important because there are specific 
optimization on execution for some of these specific data structures (also for 
translation to other engines). The consolidation could possibly be done when we 
are creating the Calcite plan?




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 541278)
    Time Spent: 0.5h  (was: 20m)

> Support column aliases in Values clause
> ---------------------------------------
>
>                 Key: HIVE-24664
>                 URL: https://issues.apache.org/jira/browse/HIVE-24664
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: Krisztian Kasa
>            Assignee: Krisztian Kasa
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Enable explicitly specify column aliases in the first row of Values clause. 
> If not all the columns has alias specified generate one.
> {code:java}
> values(1, 2 b, 3 c),(4, 5, 6);
> {code}
> {code:java}
> _col1   b   c
>   1     2   3
>   4     5   6
> {code}
>  This is not an standard SQL feature but some database engines like Impala 
> supports it.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to