You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tajo.apache.org by hyunsik <gi...@git.apache.org> on 2015/05/27 04:50:26 UTC
[GitHub] tajo pull request: TAJO-1624: Add managed table or external descri...
GitHub user hyunsik opened a pull request:
https://github.com/apache/tajo/pull/588
TAJO-1624: Add managed table or external description in Table managem…
…ent section.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/hyunsik/tajo TAJO-1624
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/tajo/pull/588.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 #588
----
commit 898107bd0816d34e35bccb7f936277c46f1638b3
Author: Hyunsik Choi <hy...@apache.org>
Date: 2015-05-27T02:49:53Z
TAJO-1624: Add managed table or external description in Table management section.
----
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo pull request: TAJO-1624: Add managed table or external descri...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/tajo/pull/588
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo pull request: TAJO-1624: Add managed table or external descri...
Posted by jihoonson <gi...@git.apache.org>.
Github user jihoonson commented on the pull request:
https://github.com/apache/tajo/pull/588#issuecomment-106122060
+1. I left a trivial comment. Please reflect before commit.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] tajo pull request: TAJO-1624: Add managed table or external descri...
Posted by jihoonson <gi...@git.apache.org>.
Github user jihoonson commented on a diff in the pull request:
https://github.com/apache/tajo/pull/588#discussion_r31194129
--- Diff: tajo-docs/src/main/sphinx/table_management/table_overview.rst ---
@@ -8,12 +8,36 @@ Overview
Managed Table
================
-.. todo::
+``CREATE TABLE`` statement with ``EXTERNAL`` keyword lets you create a table located in the warehouse directory specified by the configuration property ``tajo.warehouse.directory`` or ``${tajo.root}/warehouse`` by default. For example:
+
+.. code-block:: sql
+
+ CREATE TABLE employee (
+ id int,
+ name text,
+ age
+ );
+
External Table
================
-.. todo::
+``CREATE EXTERNAL TABLE`` statement lets you create a table located in a specify location so that Tajo does not use a default data warehouse location for the table. External tables are in common used if you already have data generated. LOCATION clause must be required for an external table.
+
+.. code-block:: sql
+
+ CREATE EXTERNAL TABLE employee (
+ id int,
+ name text,
+ age
+ ) LOCATION 'hdfs://table/path';
+
+
+The location can be a directory located in HDFS, Amazon S3, HBase, or local file system (if a Tajo cluster runs in a single machine). URI examples are as follows:
--- End diff --
Please add swift as a supported storage type.
---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---