[
https://issues.apache.org/jira/browse/DRILL-6431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sorabh Hamirwasia updated DRILL-6431:
-------------------------------------
Labels: ready-to-commit (was: )
> 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
> Labels: ready-to-commit
> 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)
