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. 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to