[
https://issues.apache.org/jira/browse/TAJO-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14362626#comment-14362626
]
ASF GitHub Bot commented on TAJO-1359:
--------------------------------------
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/422#issuecomment-81310658
I looked over the above queries.
Basically, it looks good to support the nested schema.
I have a question.
It looks that a record column and a table have the same name. In this case,
how can we identify them exactly?
Additionally, I have one suggestion.
As for tables, it would be good if we support the alias names for record
types. It will be helpful when the record column has a long name.
What do you think?
> Add nested field projector and language extension to project nested record
> --------------------------------------------------------------------------
>
> Key: TAJO-1359
> URL: https://issues.apache.org/jira/browse/TAJO-1359
> Project: Tajo
> Issue Type: Sub-task
> Components: parser, physical operator, planner/optimizer
> Reporter: Hyunsik Choi
> Assignee: Hyunsik Choi
> Fix For: 0.11.0
>
>
> We need to improve Projector class to get nested record fields, and we also
> add some language extension to specify certain nested records in table
> schema. Both works should be done together. Otherwise, we need to test an
> entire work process.
> Using dot '.' would be good for the syntax to specify nested fields. Many
> systems (Hive, Google BigQuery, and Drill) already use this syntax. Probably,
> many users are familiar with this form.
> For example, if *employee* is a root nested record field and it includes
> *age* and *name* fields, consisting two fields lastname and firstname, we can
> specify them individually as follows:
> {code}
> SELECT employee.age, employee.name.lastname, employee.name.firstname FROM ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
