[ 
https://issues.apache.org/jira/browse/IMPALA-9337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037323#comment-17037323
 ] 

ASF subversion and git services commented on IMPALA-9337:
---------------------------------------------------------

Commit f48474f3f65b1f6a9ea14b560612a65b3fa3ff33 in impala's branch 
refs/heads/master from Kris Hahn
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=f48474f ]

IMPALA-9337 [DOCS] Document new way to create external Kudu table in Impala

Summary of changes:
- Changed title of "Kudu tables:" to "Internal Kudu tables:".
- Added syntax "External Kudu tables" to show alternative create table syntax.
- Described alternative syntax and differences between resulting tables.
- In Kudu considerations, added example of creating synchronized external Kudu 
table.
- Covered external tables vs internal tables and HMS translation.

Change-Id: Ic07380fd53898dd21fbb5dacb4d9f7a84f160d4e
Reviewed-on: http://gerrit.cloudera.org:8080/15149
Reviewed-by: Vihang Karajgaonkar <vih...@cloudera.com>
Tested-by: Impala Public Jenkins <impala-public-jenk...@cloudera.com>


> Document the new way to create external Kudu tables from Impala shell
> ---------------------------------------------------------------------
>
>                 Key: IMPALA-9337
>                 URL: https://issues.apache.org/jira/browse/IMPALA-9337
>             Project: IMPALA
>          Issue Type: Documentation
>    Affects Versions: Impala 3.4.0
>            Reporter: Vihang Karajgaonkar
>            Assignee: Kris Hahn
>            Priority: Critical
>              Labels: doc
>
> IMPALA-9092 added a new way to create external Kudu tables with the purge 
> option. I think this could cause some confusion and it would be great to 
> document this option.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org

Reply via email to