[
https://issues.apache.org/jira/browse/TAJO-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14902056#comment-14902056
]
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_r40056595
--- Diff: tajo-docs/src/main/sphinx/table_management/json.rst ---
@@ -0,0 +1,100 @@
+****
+JSON
+****
+
+JSON(JavaScript Object Notation) is an open standard format for data
(de)serialization. Since it is simple and human-readable, it is popularly used
in many fields.
+Tajo supports JSON as its data format. In this section, you will get an
overview of how to create JSON tables and query on them.
+
+============================
+How to Create a JSON Table ?
+============================
+
+You can create JSON tables using ``CREATE TABLE`` statement. (For more
information, please refer to :doc:`/sql_language/ddl`.)
+For example, please consider an example data as follows:
+
+.. code-block:: bash
+
+ $ hdfs dfs -cat /table1/table.json
+ { "title" : "Hand of the King", "name" : { "first_name": "Eddard",
"last_name": "Stark"}}
+ { "title" : "Assassin", "name" : { "first_name": "Arya", "last_name":
"Stark"}}
+ { "title" : "Dancing Master", "name" : { "first_name": "Syrio",
"last_name": "Forel"}}
+
+Tajo provides two alternatives to create a table for this data. First is a
traditional way to create tables. Here is an example.
--- End diff --
How about ``two ways`` instead of ``two alternatives``?
> 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)
