[DOCS] KUDU-2051-Update Impala integration limitations

- Impala's TIMESTAMP and Kudu's UNIXTIME_MACROS from the list of limitations. - Impala now pushes down NULL/NOT NULL to Kudu. Those were removed from the list. Change-Id: I884b5c6905bc7371e7696133c53ba0df8594e945 Reviewed-on: http://gerrit.cloudera.org:8080/7355 Reviewed-by: Jean-Daniel Cryans <[email protected]> Tested-by: Kudu Jenkins
Nilkanthpatel04 · Jul 6, 2017 · 0e64b7d · 0e64b7d
1 parent 030e1a1
commit 0e64b7d
Showing 1 changed file with 3 additions and 5 deletions.
diff --git a/docs/kudu_impala_integration.adoc b/docs/kudu_impala_integration.adoc
@@ -735,12 +735,10 @@ 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.
-- Kudu tables containing `UNIXTIME_MICROS`-typed columns may not be used as an
-  external table in Impala.
-- Impala can not create Kudu tables with `TIMESTAMP`, `DECIMAL`, `VARCHAR`,
+- Impala can not create Kudu tables with `DECIMAL`, `VARCHAR`,
   or nested-typed columns.
-- Impala can not update values in primary key columns.
-- `NULL`, `NOT NULL`, `!=`, and `LIKE` predicates are not pushed to Kudu, and
+- 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
   relative to other types of predicates.
 - Updates, inserts, and deletes via Impala are non-transactional. If a query