[DOCS] Clean up trailing spaces

The pre-commit hook that used to detect
and fix trailing spaces in doc XML files
seems to have bitrotted and some trailing
spaces made it into source files during the
initial upstream cleanup.

Change-Id: Ieeb6a7d557c37be981add8353cbd1756f2e1e423
Reviewed-on: http://gerrit.cloudera.org:8080/7373
Reviewed-by: Michael Brown <mikeb@cloudera.com>
Tested-by: Impala Public Jenkins

docs/topics/impala_alter_table.xml

@@ -467,7 +467,7 @@ yes,no</codeblock>
       See <xref href="impala_perf_stats.xml#perf_table_stats_manual"/> for an example of using table properties to
       fine-tune the performance-related table statistics.
     </p>
-      
+
     <p>
       <b>To manually set or update table or column statistics:</b>
     </p>
@@ -669,7 +669,7 @@ select * from p2;
 
 alter table p2 drop column x;
 select * from p2;
-WARNINGS: 
+WARNINGS:
 File '<varname>hdfs_filename</varname>' has an incompatible Parquet schema for column 'add_columns.p2.s3'.
 Column type: STRING, Parquet schema:
 optional int32 x [i:1 d:1 r:0]

docs/topics/impala_auditing.xml

@@ -69,10 +69,10 @@ under the License.
         event log files.
       </li>
 
-      <li> 
+      <li>
         Use a cluster manager with governance capabilities to filter, visualize,
         and produce reports based on the audit logs collected
-        from all the hosts in the cluster. 
+        from all the hosts in the cluster.
       </li>
     </ul>
 
@@ -102,18 +102,18 @@ under the License.
         <codeph>fsync()</codeph> system call) to avoid loss of audit data in case of a crash.
       </p>
 
-      <p> 
+      <p>
         The runtime overhead of auditing applies to whichever host serves as the coordinator
         for the query, that is, the host you connect to when you issue the query. This might
         be the same host for all queries, or different applications or users might connect to
-        and issue queries through different hosts. 
+        and issue queries through different hosts.
       </p>
 
-      <p> 
+      <p>
         To avoid excessive I/O overhead on busy coordinator hosts, Impala syncs the audit log
         data (using the <codeph>fsync()</codeph> system call) periodically rather than after
         every query. Currently, the <codeph>fsync()</codeph> calls are issued at a fixed
-        interval, every 5 seconds. 
+        interval, every 5 seconds.
       </p>
 
       <p>
@@ -138,12 +138,12 @@ under the License.
 
     <conbody>
 
-      <p> 
+      <p>
         The audit log files represent the query information in JSON format, one query per line.
         Typically, rather than looking at the log files themselves, you should use cluster-management
         software to consolidate the log data from all Impala hosts and filter and visualize the results
         in useful ways. (If you do examine the raw log data, you might run the files through
-        a JSON pretty-printer first.) 
+        a JSON pretty-printer first.)
      </p>
 
       <p>

docs/topics/impala_compute_stats.xml

@@ -528,7 +528,7 @@ show table stats item_partitioned;
       Kudu tables. Therefore, you do not need to re-run the operation when
       you see -1 in the <codeph># Rows</codeph> column of the output from
       <codeph>SHOW TABLE STATS</codeph>. That column always shows -1 for
-      all Kudu tables. 
+      all Kudu tables.
     </p>
 
     <p conref="../shared/impala_common.xml#common/related_info"/>

docs/topics/impala_datetime_functions.xml

@@ -193,7 +193,7 @@ select now(), current_timestamp();
 | 2016-05-19 16:10:14.237849000 | 2016-05-19 16:10:14.237849000 |
 +-------------------------------+-------------------------------+
 
-select current_timestamp() as right_now,            
+select current_timestamp() as right_now,
   current_timestamp() + interval 3 hours as in_three_hours;
 +-------------------------------+-------------------------------+
 | right_now                     | in_three_hours                |
@@ -412,7 +412,7 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31
           </p>
           <p conref="../shared/impala_common.xml#common/example_blurb"/>
           <p>
-            The following example shows how comparing a <q>late</q> value with 
+            The following example shows how comparing a <q>late</q> value with
             an <q>earlier</q> value produces a positive number. In this case,
             the result is (365 * 5) + 1, because one of the intervening years is
             a leap year.
@@ -760,8 +760,8 @@ select now() as right_now,
 +-------------------------------+-----------+------------+
 
 select now() as right_now,
-  extract(day from now()) as this_day,  
-  extract(hour from now()) as this_hour;  
+  extract(day from now()) as this_day,
+  extract(hour from now()) as this_hour;
 +-------------------------------+----------+-----------+
 | right_now                     | this_day | this_hour |
 +-------------------------------+----------+-----------+

docs/topics/impala_describe.xml

@@ -737,7 +737,7 @@ Returned 27 row(s) in 0.17s</codeblock>
     </ul>
 
     <p rev="kudu">
-      The following example shows <codeph>DESCRIBE</codeph> output for a simple Kudu table, with 
+      The following example shows <codeph>DESCRIBE</codeph> output for a simple Kudu table, with
       a single-column primary key and all column attributes left with their default values:
     </p>
 

docs/topics/impala_runtime_filtering.xml

@@ -296,12 +296,12 @@ under the License.
             </li>
             <li>
               <p rev="2.6.0 IMPALA-3480">
-                <xref href="impala_runtime_filter_max_size.xml#runtime_filter_max_size"/> 
+                <xref href="impala_runtime_filter_max_size.xml#runtime_filter_max_size"/>
               </p>
             </li>
             <li>
               <p rev="2.6.0 IMPALA-3480">
-                <xref href="impala_runtime_filter_min_size.xml#runtime_filter_min_size"/> 
+                <xref href="impala_runtime_filter_min_size.xml#runtime_filter_min_size"/>
               </p>
             </li>
             <li>

docs/topics/impala_show.xml

@@ -943,7 +943,7 @@ show table stats kudu_table;
         Kudu tables. Therefore, you do not need to re-run <codeph>COMPUTE STATS</codeph>
         when you see -1 in the <codeph># Rows</codeph> column of the output from
         <codeph>SHOW TABLE STATS</codeph>. That column always shows -1 for
-        all Kudu tables. 
+        all Kudu tables.
       </p>
 
       <p conref="../shared/impala_common.xml#common/example_blurb"/>

docs/topics/impala_troubleshooting.xml

@@ -112,7 +112,7 @@ under the License.
 $ sudo sysctl -w vm.drop_caches=3 vm.drop_caches=0
 vm.drop_caches = 3
 vm.drop_caches = 0
-$ sudo dd if=/dev/sda bs=1M of=/dev/null count=1k 
+$ sudo dd if=/dev/sda bs=1M of=/dev/null count=1k
 1024+0 records in
 1024+0 records out
 1073741824 bytes (1.1 GB) copied, 5.60373 s, 192 MB/s