[ 
https://issues.apache.org/jira/browse/DRILL-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16483419#comment-16483419
 ] 

ASF GitHub Bot commented on DRILL-6431:
---------------------------------------

HanumathRao commented on issue #1277: DRILL-6431: Unnest operator requires 
table and a single column alias 
URL: https://github.com/apache/drill/pull/1277#issuecomment-390843003
 
 
   @amansinha100  Thank you for the review. Done the changes.
   
   @sohami I have done the required refactoring of the code. Please do let me 
know if it is fine.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Unnest operator requires table and a single column alias to be specified.
> -------------------------------------------------------------------------
>
>                 Key: DRILL-6431
>                 URL: https://issues.apache.org/jira/browse/DRILL-6431
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization, SQL Parser
>            Reporter: Hanumath Rao Maduri
>            Assignee: Hanumath Rao Maduri
>            Priority: Major
>             Fix For: 1.14.0
>
>
> Currently, unnest operator is not required to specify alias neither for table 
> name nor column name. This has some implications on what name the unnest 
> operator output column should use. One can use a common name like "unnest" as 
> the output name. It means, customers need to be educated on what to expect 
> from unnest operator. This might confuse some customers and also prone to 
> introduce errors in the query.
> The design decision for DRILL is that unnest always produces either a scalar 
> column or a map (depending upon the input schema for it), but it is always a 
> single column. 
> Given this scenario, it is better to enforce the requirement that unnest 
> operator requires a table alias and a column alias(single column). This can 
> help to disambiguate the column and further can easily be referenced in the 
> query.
>  



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

Reply via email to