You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by "Jihoon Son (JIRA)" <ji...@apache.org> on 2015/09/23 03:25:04 UTC

[jira] [Resolved] (TAJO-1832) Well support for self-describing data formats

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

Jihoon Son resolved TAJO-1832.
------------------------------
       Resolution: Fixed
    Fix Version/s: 0.11.0

Committed to master and 0.11.

> Well support for self-describing data formats
> ---------------------------------------------
>
>                 Key: TAJO-1832
>                 URL: https://issues.apache.org/jira/browse/TAJO-1832
>             Project: Tajo
>          Issue Type: New Feature
>          Components: Planner/Optimizer
>            Reporter: Jihoon Son
>            Assignee: Jihoon Son
>             Fix For: 0.11.0
>
>
> *Problem*
> Tajo already has a support for self-describing data formats like JSON, Parquet, or ORC. While they are capable of providing schema information by themselves, users must define schema to query on them with the current implementation. To solve this inconvenience, we have to improve our query planner to support self-describing data formats well. 
> *Solution*
> First, we need to allow omitting schema definition for the create table statement. When a query is submitted for a self-describing table, the columns which don't exist in that table will be filled with Nulls. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)