The documentation work can be finish after release. So, I reschedule it to 0.11.1.

GitHub user eminency opened a pull request:

https://github.com/apache/tajo/pull/878

TAJO-1856: Add a description about the relationship of tablespace, managed table, and external table to Tablespace section of Table Management chapter

Hi @hyunsik , @jihoonson .

One more PR, please review.

Thanks.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/eminency/tajo TAJO-1856

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/tajo/pull/878.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #878

commit bcd5e8716f7695a89afd0c6051dc54ef4936b88c
Author: Jongyoung Park <eminency@gmail.com>
Date: 2015-11-25T06:27:20Z

explanation for table and tablespace is added

commit d9b1a37d4a762126736f65228e08b87e632dc882
Author: Jongyoung Park <eminency@gmail.com>
Date: 2015-11-25T06:33:27Z

paragraph is separated

Github user jihoonson commented on a diff in the pull request:

https://github.com/apache/tajo/pull/878#discussion_r45936027

— Diff: tajo-docs/src/main/sphinx/table_management/tablespaces.rst —
@@ -1,9 +1,26 @@
-*************************************
+***********
Tablespaces
-*************************************
+***********

-Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored. Once defined, a tablespace can be referred to by name when creating a database or a table. Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.
+Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored.
+Once defined, a tablespace can be referred to by name when creating a database or a table.
+Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.

+============================================
+External Table, Managed Table and Tablespace
+============================================
+
+Tajo has two types of table. One is external table. It needs *location* property when the table is created. Using this property, you can create an external table indicating existing external data source.
+For example, if there is already your data as Text/JSON files or HBase table, you can register it as tajo external table.
+Other one is managed table, which means internal table, that is created in Tajo internal table space. You can convert external data to the form that you want and save it in managed table.
— End diff –

Tablespace is a single word.

Github user jihoonson commented on a diff in the pull request:

https://github.com/apache/tajo/pull/878#discussion_r45936372

— Diff: tajo-docs/src/main/sphinx/table_management/tablespaces.rst —
@@ -1,9 +1,26 @@
-*************************************
+***********
Tablespaces
-*************************************
+***********

-Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored. Once defined, a tablespace can be referred to by name when creating a database or a table. Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.
+Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored.
+Once defined, a tablespace can be referred to by name when creating a database or a table.
+Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.

+============================================
+External Table, Managed Table and Tablespace
+============================================
+
+Tajo has two types of table. One is external table. It needs *location* property when the table is created. Using this property, you can create an external table indicating existing external data source.
+For example, if there is already your data as Text/JSON files or HBase table, you can register it as tajo external table.
+Other one is managed table, which means internal table, that is created in Tajo internal table space. You can convert external data to the form that you want and save it in managed table.
— End diff –

The definition of managed tables is the tables which are created and managed by Tajo. One of their characteristics is that they are stored in directories under Tajo's root directory.

Github user jihoonson commented on a diff in the pull request:

https://github.com/apache/tajo/pull/878#discussion_r45937207

— Diff: tajo-docs/src/main/sphinx/table_management/tablespaces.rst —
@@ -1,9 +1,26 @@
-*************************************
+***********
Tablespaces
-*************************************
+***********

-Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored. Once defined, a tablespace can be referred to by name when creating a database or a table. Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.
+Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored.
+Once defined, a tablespace can be referred to by name when creating a database or a table.
+Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.

+============================================
+External Table, Managed Table and Tablespace
+============================================
+
+Tajo has two types of table. One is external table. It needs *location* property when the table is created. Using this property, you can create an external table indicating existing external data source.
+For example, if there is already your data as Text/JSON files or HBase table, you can register it as tajo external table.
+Other one is managed table, which means internal table, that is created in Tajo internal table space. You can convert external data to the form that you want and save it in managed table.
+
+Tablespace is used for managed tables and it is a kind of alias represents physical(distributed, usually) storages. When managed table is created, you can specify a tablespace with *tablespace* keyword, or default tablespace will be used.
— End diff –

I suggest ```Tablespace is a predefined physical location where data stored on. It is supported for only managed tables. When you create a managed table, you can use the *tablespace* keyword to specify the location of data will be stored. If the tablespace is not specified, the default tablespace of the table's database is used.```

Github user jihoonson commented on a diff in the pull request:

https://github.com/apache/tajo/pull/878#discussion_r45943420

— Diff: tajo-docs/src/main/sphinx/table_management/tablespaces.rst —
@@ -1,9 +1,26 @@
-*************************************
+***********
Tablespaces
-*************************************
+***********

-Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored. Once defined, a tablespace can be referred to by name when creating a database or a table. Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.
+Tablespaces in Tajo allow users to define locations in the storage system where the files or data objects representing database objects can be stored.
+Once defined, a tablespace can be referred to by name when creating a database or a table.
+Especially, it is very useful when a Tajo cluster instance should use heterogeneous storage systems such as HDFS, MySQL, and Oracle.

+============================================
+External Table, Managed Table and Tablespace
+============================================
+
+Tajo has two types of table. One is external table. It needs *location* property when the table is created. Using this property, you can create an external table indicating existing external data source.
+For example, if there is already your data as Text/JSON files or HBase table, you can register it as tajo external table.
+Other one is managed table, which means internal table, that is created in Tajo internal table space. You can convert external data to the form that you want and save it in managed table.
— End diff –

I made some mistakes. Tablespace's characteristic is each tablespace has a physical location and every data in a tablespace is stored there. Tajo's root directory on hdfs is an example physical locatuon of hdfs tablespace.

Github user eminency commented on the pull request:

https://github.com/apache/tajo/pull/878#issuecomment-159804277

Refined more simply, please check.

Github user jihoonson commented on the pull request:

https://github.com/apache/tajo/pull/878#issuecomment-160029639

+1 LGTM.

Github user asfgit closed the pull request at:

https://github.com/apache/tajo/pull/878

FAILURE: Integrated in Tajo-master-CODEGEN-build #606 (See https://builds.apache.org/job/Tajo-master-CODEGEN-build/606/)
TAJO-1856: Add a description about the relationship of tablespace, (jihoonson: rev ee7279d237b17401a144778a1bcbf9bbccf220f2)

• CHANGES
• tajo-docs/src/main/sphinx/table_management/tablespaces.rst

SUCCESS: Integrated in Tajo-master-build #995 (See https://builds.apache.org/job/Tajo-master-build/995/)
TAJO-1856: Add a description about the relationship of tablespace, (jihoonson: rev ee7279d237b17401a144778a1bcbf9bbccf220f2)

• tajo-docs/src/main/sphinx/table_management/tablespaces.rst
• CHANGES

ABORTED: Integrated in Tajo-0.11.1-build #116 (See https://builds.apache.org/job/Tajo-0.11.1-build/116/)
TAJO-1856: Add a description about the relationship of tablespace, (jihoonson: rev 556015c11e583dd2bc2bd2c5a287ef73302991b0)

• CHANGES
• tajo-docs/src/main/sphinx/table_management/tablespaces.rst