impala-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [4/4] incubator-impala git commit: IMPALA-3401: Suppress blocks of content devoted to Cloudera Manager.
Date Thu, 05 Jan 2017 23:59:46 GMT
IMPALA-3401: Suppress blocks of content devoted to Cloudera Manager.

Initial experiment to see how the doc looks & builds when the biggest,
most obvious pieces of Cloudera Manager-related content are suppressed:
- Primarily entire subtopics.
- In some cases, individual notes, paragraphs, and list items.
- Also the CM reference in the reused "cancel" text which showed up
  many times throughout the SQL syntax section.

Just hiding in the output for now, rather than removing from source,
because we might find there's generic material we need to hoist out of
the CM-related subtopics.

Was planning to use audience="hidden" to hide, but since that CR hasn't
landed in master yet, still using audience="Cloudera" for the moment,
and will switch attribute values later.
A little rewording of titles and suppressing smaller elements such as
paragraphs where the CM aspect didn't apply to the entire subtopic.

Change-Id: Ic799f77bc758a1cf40c53fa412bf02d852901a69
Reviewed-by: Jim Apple <>
Tested-by: John Russell <>


Branch: refs/heads/master
Commit: c4ee03a7e595e38886e6688182338a933a391285
Parents: 81c3653
Author: John Russell <>
Authored: Sun Dec 18 13:17:16 2016 -0800
Committer: John Russell <>
Committed: Thu Jan 5 23:55:45 2017 +0000

 docs/impala.ditamap                         |  4 ++--
 docs/shared/impala_common.xml               | 16 +++++++---------
 docs/topics/impala_admission.xml            |  4 ++--
 docs/topics/impala_authorization.xml        |  4 ++--
 docs/topics/impala_breakpad.xml             |  2 +-
 docs/topics/impala_cm_installation.xml      |  2 +-
 docs/topics/impala_config_options.xml       |  4 ++--
 docs/topics/impala_faq.xml                  |  8 ++++----
 docs/topics/impala_hbase.xml                |  2 +-
 docs/topics/impala_incompatible_changes.xml |  4 ++--
 docs/topics/impala_isilon.xml               |  4 ++--
 docs/topics/impala_ldap.xml                 |  5 ++++-
 docs/topics/impala_logging.xml              |  8 ++++----
 docs/topics/impala_perf_hdfs_caching.xml    |  4 ++--
 docs/topics/impala_processes.xml            |  2 +-
 docs/topics/impala_proxy.xml                | 10 +++++-----
 docs/topics/impala_scalability.xml          |  2 +-
 docs/topics/impala_ssl.xml                  |  2 +-
 docs/topics/impala_txtfile.xml              |  4 ++--
 docs/topics/impala_upgrading.xml            |  8 ++++----
 docs/topics/impala_webui.xml                |  2 +-
 21 files changed, 51 insertions(+), 50 deletions(-)
diff --git a/docs/impala.ditamap b/docs/impala.ditamap
index 0e2b03d..b3c008a 100644
--- a/docs/impala.ditamap
+++ b/docs/impala.ditamap
@@ -714,8 +714,8 @@;jqlQuery=p
   <topicref audience="standalone" href="topics/impala_install.xml#install">
   <keydef href="topics/impala_install.xml" keys="install"/>
-    <topicref href="topics/impala_cm_installation.xml#cm_installation"/>
-    <keydef href="topics/impala_cm_installation.xml" keys="cm_installation"/>
+    <topicref href="topics/impala_cm_installation.xml#cm_installation" audience="Cloudera"/>
+    <keydef href="topics/impala_cm_installation.xml" keys="cm_installation" audience="Cloudera"/>
     <topicref href="topics/impala_noncm_installation.xml#noncm_installation"/>
     <keydef href="topics/impala_noncm_installation.xml" keys="noncm_installation"/>
 <!-- Removed when Hue docs were removed from main library. Might be worth resurrecting
someday as general Impala+Hue topic. -->
diff --git a/docs/shared/impala_common.xml b/docs/shared/impala_common.xml
index 6783f43..8990dbb 100644
--- a/docs/shared/impala_common.xml
+++ b/docs/shared/impala_common.xml
@@ -576,7 +576,7 @@ under the License.
             in the <cmdname>impalad</cmdname> and <cmdname>catalogd</cmdname>configuration
-        <li>
+        <li audience="Cloudera">
             For clusters managed by Cloudera Manager, select the 
             <uicontrol>Use HDFS Rules to Map Kerberos Principals to Short Names</uicontrol>
@@ -605,7 +605,7 @@ under the License.
       Sentry logs all facts that lead up to authorization decisions at the debug level. If
you do not understand
       why Sentry is denying access, the best way to debug is to temporarily turn on debug
-        <li>
+        <li audience="Cloudera">
           In Cloudera Manager, add <codeph></codeph>
to the logging settings
           for your service through the corresponding <uicontrol>Logging Safety Valve</uicontrol>
field for the
           Impala, Hive Server 2, or Solr Server services.
@@ -2356,8 +2356,7 @@ flight_num:           INT32 SNAPPY DO:83456393 FPO:83488603 SZ:10216514/11474301
       <p id="cancel_blurb_yes">
         <b>Cancellation:</b> Can be cancelled. To cancel this statement, use
Ctrl-C from the
         <cmdname>impala-shell</cmdname> interpreter, the <uicontrol>Cancel</uicontrol>
button from the
-        <uicontrol>Watch</uicontrol> page in Hue, <uicontrol>Actions &gt;
Cancel</uicontrol> from the
-        <uicontrol>Queries</uicontrol> list in Cloudera Manager, or <uicontrol>Cancel</uicontrol>
from the list of
+        <uicontrol>Watch</uicontrol> page in Hue, or <uicontrol>Cancel</uicontrol>
from the list of
         in-flight queries (for a particular node) on the <uicontrol>Queries</uicontrol>
tab in the Impala web UI
         (port 25000).
@@ -2367,8 +2366,7 @@ flight_num:           INT32 SNAPPY DO:83456393 FPO:83488603 SZ:10216514/11474301
         <codeph>COMPUTE STATS</codeph>) can be cancelled during some stages,
when running <codeph>INSERT</codeph>
         or <codeph>SELECT</codeph> operations internally. To cancel this statement,
use Ctrl-C from the
         <cmdname>impala-shell</cmdname> interpreter, the <uicontrol>Cancel</uicontrol>
button from the
-        <uicontrol>Watch</uicontrol> page in Hue, <uicontrol>Actions &gt;
Cancel</uicontrol> from the
-        <uicontrol>Queries</uicontrol> list in Cloudera Manager, or <uicontrol>Cancel</uicontrol>
from the list of
+        <uicontrol>Watch</uicontrol> page in Hue, or <uicontrol>Cancel</uicontrol>
from the list of
         in-flight queries (for a particular node) on the <uicontrol>Queries</uicontrol>
tab in the Impala web UI
         (port 25000).
@@ -3126,7 +3124,7 @@ select * from header_line limit 10;
             Other security settings may prevent Impala from writing core dumps even when
this option is enabled.
-        <li rev="CDH-34070">
+        <li rev="CDH-34070" audience="Cloudera">
             On systems managed by Cloudera Manager, the default location for core dumps is
on a temporary
             filesystem, which can lead to out-of-space issues if the core dumps are large,
frequent, or
@@ -3189,7 +3187,7 @@ sudo pip-python install ssl</codeblock>
         <codeph>SYNC_DDL</codeph> query option.
-      <p rev="1.2" id="cm48_upgrade">
+      <p rev="1.2" id="cm48_upgrade" audience="Cloudera"><!-- conref'ed in 2 places
under 'incompatible changes' -->
         In a Cloudera Manager environment, the catalog service is not recognized or managed
by Cloudera Manager
         versions prior to 4.8. Cloudera Manager 4.8 and higher require the catalog service
to be present for
         Impala. Therefore, if you upgrade to Cloudera Manager 4.8 or higher, you must also
upgrade Impala to 1.2.1
@@ -3658,7 +3656,7 @@ sudo pip-python install ssl</codeblock>
-          <li>
+          <li audience="Cloudera">
             <p rev="OPSAPS-26483">
               On systems managed by Cloudera Manager, include this value in the configuration
               <uicontrol>Java Heap Size of Catalog Server in Bytes</uicontrol>
(Cloudera Manager 5.7 and higher), or
diff --git a/docs/topics/impala_admission.xml b/docs/topics/impala_admission.xml
index 51f1fbf..0c55e69 100644
--- a/docs/topics/impala_admission.xml
+++ b/docs/topics/impala_admission.xml
@@ -606,7 +606,7 @@ under the License.
-    <concept id="admission_config_cm">
+    <concept id="admission_config_cm" audience="Cloudera">
 <!-- TK: Maybe all this stuff overlaps with admin_impala_admission_control and can be
delegated there. -->
@@ -708,7 +708,7 @@ impala.admission-control.pool-queue-timeout-ms.<varname>queue_name</varname></ph
-        <section id="section_fqn_qgb_rq">
+        <section id="section_fqn_qgb_rq" audience="Cloudera">
           <title>Example Admission Control Configurations Using Cloudera Manager</title>
diff --git a/docs/topics/impala_authorization.xml b/docs/topics/impala_authorization.xml
index 646b8d2..a844ac3 100644
--- a/docs/topics/impala_authorization.xml
+++ b/docs/topics/impala_authorization.xml
@@ -222,7 +222,7 @@ under the License.
-        <li>
+        <li audience="Cloudera">
             In an environment managed by Cloudera Manager, the server name is specified through
             <menucascade><uicontrol>Impala (Service-Wide)</uicontrol><uicontrol>Category</uicontrol><uicontrol>Advanced</uicontrol><uicontrol>Sentry
Service</uicontrol></menucascade> and
@@ -1586,7 +1586,7 @@ column-level security was by creating views that referenced particular
sets of c
-  <concept id="sentry_cm">
+  <concept id="sentry_cm" audience="Cloudera">
     <title>Managing Sentry for Impala through Cloudera Manager</title>
diff --git a/docs/topics/impala_breakpad.xml b/docs/topics/impala_breakpad.xml
index 79e491c..b437da3 100644
--- a/docs/topics/impala_breakpad.xml
+++ b/docs/topics/impala_breakpad.xml
@@ -85,7 +85,7 @@ under the License.
         <!-- Location stated in IMPALA-3581; overridden by different location from IMPALA-2686?
-          <li>
+          <li audience="Cloudera">
               Clusters managed by Cloudera Manager: <filepath>/var/log/impala-minidumps/<varname>daemon_name</varname></filepath>
diff --git a/docs/topics/impala_cm_installation.xml b/docs/topics/impala_cm_installation.xml
index 7a4ad60..a7aea7b 100644
--- a/docs/topics/impala_cm_installation.xml
+++ b/docs/topics/impala_cm_installation.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
 under the License.
 <!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="cm_installation">
+<concept id="cm_installation" audience="Cloudera">
   <title>Installing Impala with Cloudera Manager</title>
diff --git a/docs/topics/impala_config_options.xml b/docs/topics/impala_config_options.xml
index 1346fe3..bc91f9d 100644
--- a/docs/topics/impala_config_options.xml
+++ b/docs/topics/impala_config_options.xml
@@ -66,7 +66,7 @@ under the License.
-  <concept id="config_options_cm">
+  <concept id="config_options_cm" audience="Cloudera">
     <title>Configuring Impala Startup Options through Cloudera Manager</title>
@@ -243,7 +243,7 @@ Starting Impala Catalog Server:                            [  OK  ]</codeblock>
 <codeblock>export ENABLE_CORE_DUMPS=${ENABLE_COREDUMPS:-true}</codeblock>
-          <p>
+          <p audience="Cloudera">
             On systems managed by Cloudera Manager, enable the <uicontrol>Enable Core
             Dump</uicontrol> setting for the Impala service.
diff --git a/docs/topics/impala_faq.xml b/docs/topics/impala_faq.xml
index a3fb3cd..6988b8d 100644
--- a/docs/topics/impala_faq.xml
+++ b/docs/topics/impala_faq.xml
@@ -52,7 +52,7 @@ under the License.
         FAQs in this category:
-      <section id="faq_tryout">
+      <section id="faq_tryout" audience="Cloudera">
         <title>How do I try Impala out?</title>
@@ -73,7 +73,7 @@ under the License.
-      <section id="faq_demo_vm">
+      <section id="faq_demo_vm" audience="Cloudera">
         <title>Does Cloudera offer a VM for demonstrating Impala?</title>
@@ -409,7 +409,7 @@ through the <codeph>DEFAULT_ORDER_BY_LIMIT</codeph> query
       <section id="faq_cpu_prereq">
-        <title>What processor type and speed does Cloudera recommend?</title>
+        <title>What processor type and speed work best for Impala?</title>
         <sectiondiv id="faq_cpu_req">
@@ -473,7 +473,7 @@ through the <codeph>DEFAULT_ORDER_BY_LIMIT</codeph> query
               information about Impala performance optimizations and tuning techniques for
-            <li>
+            <li audience="Cloudera">
               Using Cloudera Manager, you can deploy and manage your Impala services. Cloudera
Manager is the best
               way to get started with Impala on your cluster.
diff --git a/docs/topics/impala_hbase.xml b/docs/topics/impala_hbase.xml
index 4cb3344..6f7daf3 100644
--- a/docs/topics/impala_hbase.xml
+++ b/docs/topics/impala_hbase.xml
@@ -162,7 +162,7 @@ under the License.
-      <p>
+      <p audience="Cloudera">
         Currently, Cloudera Manager does not have an Impala-only override for HBase settings,
so any HBase
         configuration change you make through Cloudera Manager would take affect for all
HBase applications.
         Therefore, this change is not recommended on systems managed by Cloudera Manager.
diff --git a/docs/topics/impala_incompatible_changes.xml b/docs/topics/impala_incompatible_changes.xml
index 52be2af..9fad426 100644
--- a/docs/topics/impala_incompatible_changes.xml
+++ b/docs/topics/impala_incompatible_changes.xml
@@ -1276,7 +1276,7 @@ select * from `cross`;</codeblock>
         to Impala 1.2.x in general.
-      <p conref="../shared/impala_common.xml#common/cm48_upgrade"/>
+      <p audience="Cloudera" conref="../shared/impala_common.xml#common/cm48_upgrade"/>
 <!-- <note conref="common.xml#common/cdh4_cdh5_upgrade"/> -->
@@ -1318,7 +1318,7 @@ select * from `cross`;</codeblock>
-      <p conref="../shared/impala_common.xml#common/cm48_upgrade"/>
+      <p audience="Cloudera" conref="../shared/impala_common.xml#common/cm48_upgrade"/>
 <!--  <note conref="common.xml#common/cdh4_cdh5_upgrade"/> -->
diff --git a/docs/topics/impala_isilon.xml b/docs/topics/impala_isilon.xml
index 9bc426d..8de8e4f 100644
--- a/docs/topics/impala_isilon.xml
+++ b/docs/topics/impala_isilon.xml
@@ -103,7 +103,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN);
       for the <cmdname>impalad</cmdname> daemon on clusters not using Cloudera
-    <p>
+    <p audience="Cloudera">
       For information about tasks performed on
       Isilon OneFS, see the information hub for Cloudera on the EMC Community Network:
@@ -117,7 +117,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN);
     <!-- <p outputclass="toc inpage"/> -->
-<concept id="isilon_cm_configs">
+<concept id="isilon_cm_configs" audience="Cloudera">
 <title>Required Configurations</title>
 <p>Specify the following configurations in Cloudera Manager on the <menucascade><uicontrol>Clusters</uicontrol><uicontrol><varname>Isilon
tab:<ul id="ul_vpx_bw5_vv">
diff --git a/docs/topics/impala_ldap.xml b/docs/topics/impala_ldap.xml
index 343d547..3100088 100644
--- a/docs/topics/impala_ldap.xml
+++ b/docs/topics/impala_ldap.xml
@@ -187,6 +187,9 @@ under the License.
       <p rev="CDH-26854">
         For clusters not managed by Cloudera Manager,
         specify the option on the <cmdname>impalad</cmdname> command line.
+      </p>
+      <p audience="Cloudera">
         For clusters managed by Cloudera Manager 5.4.0 and higher,
         search for the configuration field names <codeph>ldap_domain</codeph>,
         <codeph>ldap_basedn</codeph>, or <codeph>ldap_bind_pattern</codeph>,
@@ -300,7 +303,7 @@ username, for example <codeph></codeph>.
-      <section id="ldap_impala_hue_cm">
+      <section id="ldap_impala_hue_cm" audience="Cloudera">
         <title>Enabling LDAP for Impala in Hue Using Cloudera Manager</title>
diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml
index dbbea4b..40399ef 100644
--- a/docs/topics/impala_logging.xml
+++ b/docs/topics/impala_logging.xml
@@ -167,7 +167,7 @@ under the License.
-        <li>
+        <li audience="Cloudera">
           Cloudera Manager has an Impala configuration setting that sets the <codeph>-logbuflevel</codeph>
@@ -179,7 +179,7 @@ under the License.
   <concept id="logs_cm_noncm">
-    <title>Managing Impala Logs through Cloudera Manager or Manually</title>
+    <title>Managing Impala Logs</title>
       <data name="Category" value="Administrators"/>
@@ -189,7 +189,7 @@ under the License.
-      <p>
+      <p rev="upstream" audience="Cloudera"><!-- Whole paragraph can probably go.
         <ph rev="upstream">Cloudera</ph> recommends installing Impala through
the Cloudera Manager administration interface. To assist with
         troubleshooting, Cloudera Manager collects front-end and back-end logs together into
a single view, and let
         you do a search across log data for all the managed nodes rather than examining the
logs on each node
@@ -250,7 +250,7 @@ under the License.
         Linux tool or technique of choice. A value of 1 preserves only the very latest log
-      <p>
+      <p audience="Cloudera">
         To set up log rotation on a system managed by Cloudera Manager 5.4.0 and higher,
search for the
         <codeph>max_log_files</codeph> option name and set the appropriate value
for the <userinput>Maximum Log
         Files</userinput> field for each Impala configuration category (Impala, Catalog
Server, and StateStore).
diff --git a/docs/topics/impala_perf_hdfs_caching.xml b/docs/topics/impala_perf_hdfs_caching.xml
index c8f168c..017c436 100644
--- a/docs/topics/impala_perf_hdfs_caching.xml
+++ b/docs/topics/impala_perf_hdfs_caching.xml
@@ -469,11 +469,11 @@ Found 122 entries
-      <p>
+      <p audience="Cloudera">
         <b>Cloudera Manager:</b>
-      <ul>
+      <ul audience="Cloudera">
           You can enable or disable HDFS caching through Cloudera Manager, using the configuration
           <uicontrol>Maximum Memory Used for Caching</uicontrol> for the HDFS
service. This control sets the HDFS
diff --git a/docs/topics/impala_processes.xml b/docs/topics/impala_processes.xml
index 0a54823..6bba031 100644
--- a/docs/topics/impala_processes.xml
+++ b/docs/topics/impala_processes.xml
@@ -69,7 +69,7 @@ under the License.
     <p outputclass="toc inpage"/>
-  <concept id="starting_via_cm">
+  <concept id="starting_via_cm" audience="Cloudera">
     <title>Starting Impala through Cloudera Manager</title>
diff --git a/docs/topics/impala_proxy.xml b/docs/topics/impala_proxy.xml
index c225cce..f064961 100644
--- a/docs/topics/impala_proxy.xml
+++ b/docs/topics/impala_proxy.xml
@@ -143,7 +143,7 @@ under the License.
           Run the load-balancing proxy server, pointing it at the configuration file that
you set up.
-        <li>
+        <li audience="Cloudera">
           On systems managed by Cloudera Manager, on the page
           Default Group</uicontrol></menucascade>, specify a value for the <uicontrol>Impala
Daemons Load
@@ -269,7 +269,7 @@ under the License.
           running the <cmdname>impalad</cmdname> daemon.
-        <li rev="CDH-40363">
+        <li rev="CDH-40363" audience="Cloudera">
           For a cluster managed by Cloudera Manager (5.4.2 or higher), fill in the Impala
configuration setting
           <uicontrol>Impala Daemons Load Balancer</uicontrol> with the appropriate
host:port combination.
           Then restart the Impala service.
@@ -320,7 +320,7 @@ under the License.
                 configuration snippet, add: <codeblock>--principal=impala/<varname>proxy_host</varname>@<varname>realm</varname>
-                <note>
+                <note audience="Cloudera">
                   <p>On a cluster managed by Cloudera Manager 5.1 (or higher),
                     when you set up Kerberos authentication using the wizard, you
                     can choose to allow Cloudera Manager to deploy the
@@ -335,7 +335,7 @@ under the License.
-              <li>
+              <li audience="Cloudera">
                 On a cluster managed by Cloudera Manager, create a role group to set the
configuration values from
                 the preceding step on a per-host basis.
@@ -352,7 +352,7 @@ under the License.
             Restart Impala to make the changes take effect. Follow the appropriate steps
depending on whether you use
             Cloudera Manager or not:
-              <li>
+              <li audience="Cloudera">
                 On a cluster managed by Cloudera Manager, restart the Impala service.
diff --git a/docs/topics/impala_scalability.xml b/docs/topics/impala_scalability.xml
index ca567ea..69bd08f 100644
--- a/docs/topics/impala_scalability.xml
+++ b/docs/topics/impala_scalability.xml
@@ -469,7 +469,7 @@ Memory Usage: Additional Notes
-            <li>
+            <li audience="Cloudera">
               The <uicontrol>Impala Queries</uicontrol> dialog in Cloudera Manager.
You can see the peak memory
               usage for a query, combined across all nodes in the cluster.
diff --git a/docs/topics/impala_ssl.xml b/docs/topics/impala_ssl.xml
index 3efd1d3..7375cfd 100644
--- a/docs/topics/impala_ssl.xml
+++ b/docs/topics/impala_ssl.xml
@@ -56,7 +56,7 @@ under the License.
-  <concept id="concept_gnk_2tt_qp">
+  <concept id="concept_gnk_2tt_qp" audience="Cloudera">
     <title>Using Cloudera Manager</title>
diff --git a/docs/topics/impala_txtfile.xml b/docs/topics/impala_txtfile.xml
index 0b81ca9..f23d4d7 100644
--- a/docs/topics/impala_txtfile.xml
+++ b/docs/topics/impala_txtfile.xml
@@ -483,11 +483,11 @@ INSERT INTO csv SELECT * FROM other_file_format_table;</codeblock>
             <b>Prepare your systems to work with LZO by downloading and installing
the appropriate libraries:</b>
-            <p>
+            <p audience="Cloudera">
               <b>On systems managed by Cloudera Manager using parcels:</b>
-            <p>
+            <p audience="Cloudera">
               See the setup instructions for the LZO parcel in the Cloudera Manager documentation
               <xref href=""
scope="external" format="html">Cloudera
               Manager 5</xref>.
diff --git a/docs/topics/impala_upgrading.xml b/docs/topics/impala_upgrading.xml
index 837330b..3fea37b 100644
--- a/docs/topics/impala_upgrading.xml
+++ b/docs/topics/impala_upgrading.xml
@@ -47,7 +47,7 @@ under the License.
           upgrade from CDH 4 to the latest CDH 5, which also has the latest Impala.
-        <li rev="ver">
+        <li rev="ver" audience="Cloudera">
           When you upgrade Impala, also upgrade Cloudera Manager if necessary:
@@ -92,7 +92,7 @@ under the License.
     <p outputclass="toc inpage"/>
-  <concept id="upgrade_cm_parcels">
+  <concept id="upgrade_cm_parcels" audience="Cloudera">
     <title>Upgrading Impala through Cloudera Manager - Parcels</title>
@@ -170,7 +170,7 @@ sudo apt-get purge <varname>pkg_names</varname> # Ubuntu,
-  <concept id="upgrade_cm_pkgs">
+  <concept id="upgrade_cm_pkgs" audience="Cloudera">
     <title>Upgrading Impala through Cloudera Manager - Packages</title>
@@ -253,7 +253,7 @@ $ sudo apt-get install hadoop-lzo-cdh4 # Optional; if this package is
already in
-  <concept id="upgrade_noncm">
+  <concept id="upgrade_noncm" rev="upstream">
     <title>Upgrading Impala without Cloudera Manager</title>
diff --git a/docs/topics/impala_webui.xml b/docs/topics/impala_webui.xml
index c90d812..612b882 100644
--- a/docs/topics/impala_webui.xml
+++ b/docs/topics/impala_webui.xml
@@ -104,7 +104,7 @@ under the License.
         suspect is having problems.
-      <note>
+      <note audience="Cloudera">
         To get a convenient picture of the health of all Impala nodes in a cluster, use the
Cloudera Manager
         interface, which collects the low-level operational information from all Impala nodes,
and presents a
         unified view of the entire cluster.

View raw message