[
https://issues.apache.org/jira/browse/TAJO-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902052#comment-14902052
]
ASF GitHub Bot commented on TAJO-1832:
--------------------------------------
Github user hyunsik commented on a diff in the pull request:
https://github.com/apache/tajo/pull/756#discussion_r40056479
--- Diff: tajo-docs/src/main/sphinx/sql_language/ddl.rst ---
@@ -40,7 +40,7 @@ CREATE TABLE
CREATE TABLE [IF NOT EXISTS] <table_name> [(<column_name> <data_type>,
... )] [TABLESPACE tablespace_name]
[using <storage_type> [with (<key> = <value>, ...)]] [AS
<select_statement>]
- CREATE EXTERNAL TABLE [IF NOT EXISTS] <table_name> (<column_name>
<data_type>, ... )
+ CREATE EXTERNAL TABLE [IF NOT EXISTS] <table_name> [(<column_name>
<data_type>, ... )]
--- End diff --
The documentation needs to reflect the changed DDL for ``(*)``.
> 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
>
> *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)
