[kudu] branch master updated: [docs] Impala can create Kudu tables with VARCHAR columns

[al...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

alexey pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/kudu.git


The following commit(s) were added to refs/heads/master by this push:
     new 3dcb511  [docs] Impala can create Kudu tables with VARCHAR columns
3dcb511 is described below

commit 3dcb51190792c360c3718ff48ebfb8797a1b19b3
Author: Alexey Serbin <al...@apache.org>
AuthorDate: Tue Nov 9 18:40:39 2021 -0800

    [docs] Impala can create Kudu tables with VARCHAR columns
    
    It's now possible to create Kudu tables with VARCHAR columns using
    impala-shell since KUDU-1938 and IMPALA-5092 have been addressed.
    
    Change-Id: Id41b30015b3a5d6ede4f39325fe25e31959fede6
    Reviewed-on: http://gerrit.cloudera.org:8080/18008
    Tested-by: Kudu Jenkins
    Reviewed-by: Attila Bukor <ab...@apache.org>
---
 docs/kudu_impala_integration.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/kudu_impala_integration.adoc b/docs/kudu_impala_integration.adoc
index 48b2ef7..0def047 100755
--- a/docs/kudu_impala_integration.adoc
+++ b/docs/kudu_impala_integration.adoc
@@ -786,7 +786,7 @@ The examples above have only explored a fraction of what you can do with Impala
   to work around this issue.
 - When creating a Kudu table, the `CREATE TABLE` statement must include the
   primary key columns before other columns, in primary key order.
-- Impala can not create Kudu tables with `VARCHAR` or nested-typed columns.
+- Impala can not create Kudu tables with nested-typed columns.
 - Impala cannot update values in primary key columns.
 - `!=` and `LIKE` predicates are not pushed to Kudu, and
   instead will be evaluated by the Impala scan node. This may decrease performance