You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2015/05/06 10:48:01 UTC

[jira] [Updated] (TAJO-1359) Add nested field projector and language extension to project nested record

     [ https://issues.apache.org/jira/browse/TAJO-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyunsik Choi updated TAJO-1359:
-------------------------------
    Attachment: TAJO-1359_5.patch

I rebased the patch against the recent changes.

> 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
>
>         Attachments: TAJO-1359.patch, TAJO-1359_2.patch, TAJO-1359_3.patch, TAJO-1359_4.patch, TAJO-1359_5.patch
>
>
> 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)