[DOCS] Genericize 'cluster sizing' topic

A rather vendor-specific 'consult Cloudera' reference
to reword.

Change-Id: I25f9269596b2106558e2c5c0e66096cab64dc2f4
Reviewed-on: http://gerrit.cloudera.org:8080/6365
Reviewed-by: Ambreen Kazi <[email protected]>
Reviewed-by: John Russell <[email protected]>
Tested-by: Impala Public Jenkins


Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/c4ffc338
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/c4ffc338
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/c4ffc338

Branch: refs/heads/master
Commit: c4ffc3384f06d44c49096ba4e4c5ff24fa781c35
Parents: ab23e16
Author: John Russell <[email protected]>
Authored: Mon Mar 13 10:39:27 2017 -0700
Committer: Impala Public Jenkins <[email protected]>
Committed: Mon Mar 13 22:02:22 2017 +0000

----------------------------------------------------------------------
 docs/topics/impala_cluster_sizing.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/c4ffc338/docs/topics/impala_cluster_sizing.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_cluster_sizing.xml 
b/docs/topics/impala_cluster_sizing.xml
index 9708644..7b395c5 100644
--- a/docs/topics/impala_cluster_sizing.xml
+++ b/docs/topics/impala_cluster_sizing.xml
@@ -51,8 +51,8 @@ under the License.
     </p>
 
     <note>
-      Before making purchase or deployment decisions, consult your Cloudera 
representative to verify the
-      conclusions about hardware requirements based on your data volume and 
workload.
+      Before making purchase or deployment decisions, consult organizations 
with relevant experience
+      to verify the conclusions about hardware requirements based on your data 
volume and workload.
     </note>
 
 <!--    <p outputclass="toc inpage"/> -->

Reply via email to