kudu git commit: Impala integration doc: clarify partitioning recommendations

[da...@apache.org]

Repository: kudu
Updated Branches:
  refs/heads/master b9cce6e01 -> 946004aee


Impala integration doc: clarify partitioning recommendations

Change-Id: I67505f7a6aaa3c065877e742aaa7b77cf8394b55
Reviewed-on: http://gerrit.cloudera.org:8080/8714
Reviewed-by: Will Berkeley <wd...@gmail.com>
Tested-by: Dan Burkert <da...@apache.org>


Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/946004ae
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/946004ae
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/946004ae

Branch: refs/heads/master
Commit: 946004aeed4ce2844c2cd14bbf2077b419de3c49
Parents: b9cce6e
Author: Dan Burkert <da...@apache.org>
Authored: Fri Dec 1 10:06:14 2017 -0800
Committer: Dan Burkert <da...@apache.org>
Committed: Fri Dec 1 18:21:25 2017 +0000

----------------------------------------------------------------------
 docs/kudu_impala_integration.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/kudu/blob/946004ae/docs/kudu_impala_integration.adoc
----------------------------------------------------------------------
diff --git a/docs/kudu_impala_integration.adoc b/docs/kudu_impala_integration.adoc
index c176158..dc5b990 100755
--- a/docs/kudu_impala_integration.adoc
+++ b/docs/kudu_impala_integration.adoc
@@ -501,8 +501,8 @@ stored in the dropped partition.
 
 - For large tables, such as fact tables, aim for as many tablets as you have
   cores in the cluster.
-- For small tables, such as dimension tables, aim for a large enough number of tablets
-  that each tablet is at least 1 GB in size.
+- For small tables, such as dimension tables, ensure that each tablet is at
+  least 1 GB in size.
 
 In general, be mindful the number of tablets limits the parallelism of reads,
 in the current implementation. Increasing the number of tablets significantly
@@ -731,7 +731,7 @@ The examples above have only explored a fraction of what you can do with Impala
 - Kudu tables with a name containing upper case or non-ascii characters must be
   assigned an alternate name when used as an external table in Impala.
 - Kudu tables with a column name containing upper case or non-ascii characters
-  may not be used as an external table in Impala. Columns may be renamed in Kudu 
+  may not be used as an external table in Impala. Columns may be renamed in Kudu
   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.
@@ -745,4 +745,4 @@ The examples above have only explored a fraction of what you can do with Impala
   fails part of the way through, its partial effects will not be rolled back.
 - The maximum parallelism of a single query is limited to the number of tablets
   in a table. For good analytic performance, aim for 10 or more tablets per host
-  or use large tables.
+  for large tables.