http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_datetime_functions.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_datetime_functions.xml b/docs/topics/impala_datetime_functions.xml index 08a1036..4276c88 100644 --- a/docs/topics/impala_datetime_functions.xml +++ b/docs/topics/impala_datetime_functions.xml @@ -89,7 +89,7 @@ months_between </dt> <dd> - <indexterm audience="Cloudera">add_months() function</indexterm> + <indexterm audience="hidden">add_months() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of months. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -141,7 +141,7 @@ select now(), add_months(now(), -1); </dt> <dd> - <indexterm audience="Cloudera">adddate() function</indexterm> + <indexterm audience="hidden">adddate() function</indexterm> <b>Purpose:</b> Adds a specified number of days to a <codeph>TIMESTAMP</codeph> value. Similar to <codeph>date_add()</codeph>, but starts with an actual <codeph>TIMESTAMP</codeph> value instead of a string that is converted to a <codeph>TIMESTAMP</codeph>. @@ -179,7 +179,7 @@ select now() as right_now, adddate(now(), -15) as now_minus_15; </dt> <dd> - <indexterm audience="Cloudera">current_timestamp() function</indexterm> + <indexterm audience="hidden">current_timestamp() function</indexterm> <b>Purpose:</b> Alias for the <codeph>now()</codeph> function. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -213,7 +213,7 @@ select current_timestamp() as right_now, </dt> <dd> - <indexterm audience="Cloudera">date_add() function</indexterm> + <indexterm audience="hidden">date_add() function</indexterm> <b>Purpose:</b> Adds a specified number of days to a <codeph>TIMESTAMP</codeph> value. <!-- Found this not to be true in latest release. I think the signature changed way back. The first argument @@ -287,7 +287,7 @@ select date_add(cast('2016-01-31' as timestamp), interval 3 months) as 'april_31 </dt> <dd> - <indexterm audience="Cloudera">date_part() function</indexterm> + <indexterm audience="hidden">date_part() function</indexterm> <b>Purpose:</b> Similar to <xref href="impala_datetime_functions.xml#datetime_functions/extract"><codeph>EXTRACT()</codeph></xref>, with the argument order reversed. Supports the same date and time units as <codeph>EXTRACT()</codeph>. @@ -323,7 +323,7 @@ select date_part('hour',now()) as hour_of_day; </dt> <dd> - <indexterm audience="Cloudera">date_sub() function</indexterm> + <indexterm audience="hidden">date_sub() function</indexterm> <b>Purpose:</b> Subtracts a specified number of days from a <codeph>TIMESTAMP</codeph> value. <!-- Found this not to be true in latest release. I think the signature changed way back. The first argument can be a string, which is automatically cast to <codeph>TIMESTAMP</codeph> if it uses the @@ -396,7 +396,7 @@ select date_sub(cast('2016-05-31' as timestamp), interval 1 months) as 'april_31 </dt> <dd> - <indexterm audience="Cloudera">datediff() function</indexterm> + <indexterm audience="hidden">datediff() function</indexterm> <b>Purpose:</b> Returns the number of days between two <codeph>TIMESTAMP</codeph> values. <p> <b>Return type:</b> <codeph>int</codeph> @@ -474,7 +474,7 @@ select now() as right_now, datediff(now(), now() - interval 18 hours) as 18_hour </dt> <dd> - <indexterm audience="Cloudera">day() function</indexterm> + <indexterm audience="hidden">day() function</indexterm> <b>Purpose:</b> Returns the day field from the date portion of a <codeph>TIMESTAMP</codeph>. The value represents the day of the month, therefore is in the range 1-31, or less for months without 31 days. @@ -549,7 +549,7 @@ select day('2016-02-028'); </dt> <dd> - <indexterm audience="Cloudera">dayname() function</indexterm> + <indexterm audience="hidden">dayname() function</indexterm> <b>Purpose:</b> Returns the day field from a <codeph>TIMESTAMP</codeph> value, converted to the string corresponding to that day name. The range of return values is <codeph>'Sunday'</codeph> to <codeph>'Saturday'</codeph>. Used in report-generating queries, as an alternative to calling @@ -593,7 +593,7 @@ select now() + interval 1 day as tomorrow, </dt> <dd> - <indexterm audience="Cloudera">dayofweek() function</indexterm> + <indexterm audience="hidden">dayofweek() function</indexterm> <b>Purpose:</b> Returns the day field from the date portion of a <codeph>TIMESTAMP</codeph>, corresponding to the day of the week. The range of return values is 1 (Sunday) to 7 (Saturday). <p> @@ -621,7 +621,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">dayofyear() function</indexterm> + <indexterm audience="hidden">dayofyear() function</indexterm> <b>Purpose:</b> Returns the day field from a <codeph>TIMESTAMP</codeph> value, corresponding to the day of the year. The range of return values is 1 (January 1) to 366 (December 31 of a leap year). <p> @@ -664,7 +664,7 @@ select now() - interval 1 year as last_year, </dt> <dd> - <indexterm audience="Cloudera">days_add() function</indexterm> + <indexterm audience="hidden">days_add() function</indexterm> <b>Purpose:</b> Adds a specified number of days to a <codeph>TIMESTAMP</codeph> value. Similar to <codeph>date_add()</codeph>, but starts with an actual <codeph>TIMESTAMP</codeph> value instead of a string that is converted to a <codeph>TIMESTAMP</codeph>. @@ -692,7 +692,7 @@ select now() as right_now, days_add(now(), 31) as 31_days_later; </dt> <dd> - <indexterm audience="Cloudera">days_sub() function</indexterm> + <indexterm audience="hidden">days_sub() function</indexterm> <b>Purpose:</b> Subtracts a specified number of days from a <codeph>TIMESTAMP</codeph> value. Similar to <codeph>date_sub()</codeph>, but starts with an actual <codeph>TIMESTAMP</codeph> value instead of a string that is converted to a <codeph>TIMESTAMP</codeph>. @@ -719,7 +719,7 @@ select now() as right_now, days_sub(now(), 31) as 31_days_ago; </dt> <dd> - <indexterm audience="Cloudera">extract() function</indexterm> + <indexterm audience="hidden">extract() function</indexterm> <b>Purpose:</b> Returns one of the numeric date or time fields from a <codeph>TIMESTAMP</codeph> value. <p> <b>Unit argument:</b> The <codeph>unit</codeph> string can be one of <codeph>year</codeph>, @@ -778,7 +778,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">from_unixtime() function</indexterm> + <indexterm audience="hidden">from_unixtime() function</indexterm> <b>Purpose:</b> Converts the number of seconds from the Unix epoch to the specified time into a string in the local time zone. <p> @@ -854,7 +854,7 @@ select from_unixtime(1392394861,"HH:mm:ss"); </dt> <dd> - <indexterm audience="Cloudera">from_utc_timestamp() function</indexterm> + <indexterm audience="hidden">from_utc_timestamp() function</indexterm> <b>Purpose:</b> Converts a specified UTC timestamp value into the appropriate value for a specified time zone. <p> @@ -921,7 +921,7 @@ select '2016-01-05' as local_datetime, </dt> <dd> - <indexterm audience="Cloudera">hour() function</indexterm> + <indexterm audience="hidden">hour() function</indexterm> <b>Purpose:</b> Returns the hour field from a <codeph>TIMESTAMP</codeph> field. <p> <b>Return type:</b> <codeph>int</codeph> @@ -955,7 +955,7 @@ select now() + interval 12 hours as 12_hours_from_now, </dt> <dd> - <indexterm audience="Cloudera">hours_add() function</indexterm> + <indexterm audience="hidden">hours_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of hours. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -982,7 +982,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">hours_sub() function</indexterm> + <indexterm audience="hidden">hours_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of hours. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1008,7 +1008,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">int_months_between() function</indexterm> + <indexterm audience="hidden">int_months_between() function</indexterm> <b>Purpose:</b> Returns the number of months between the date portions of two <codeph>TIMESTAMP</codeph> values, as an <codeph>INT</codeph> representing only the full months that passed. <p> @@ -1089,7 +1089,7 @@ select int_months_between('2015-03-31', '2015-01-30'); </dt> <dd> - <indexterm audience="Cloudera">microseconds_add() function</indexterm> + <indexterm audience="hidden">microseconds_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of microseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1116,7 +1116,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">microseconds_sub() function</indexterm> + <indexterm audience="hidden">microseconds_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of microseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1142,7 +1142,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">millisecond() function</indexterm> + <indexterm audience="hidden">millisecond() function</indexterm> <b>Purpose:</b> Returns the millisecond portion of a <codeph>TIMESTAMP</codeph> value. <p> <b>Return type:</b> <codeph>int</codeph> @@ -1185,7 +1185,7 @@ select now(), millisecond(now()); </dt> <dd> - <indexterm audience="Cloudera">milliseconds_add() function</indexterm> + <indexterm audience="hidden">milliseconds_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of milliseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1212,7 +1212,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">milliseconds_sub() function</indexterm> + <indexterm audience="hidden">milliseconds_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of milliseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1238,7 +1238,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">minute() function</indexterm> + <indexterm audience="hidden">minute() function</indexterm> <b>Purpose:</b> Returns the minute field from a <codeph>TIMESTAMP</codeph> value. <p> <b>Return type:</b> <codeph>int</codeph> @@ -1264,7 +1264,7 @@ select now() as right_now, minute(now()) as current_minute; </dt> <dd> - <indexterm audience="Cloudera">minutes_add() function</indexterm> + <indexterm audience="hidden">minutes_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of minutes. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1290,7 +1290,7 @@ select now() as right_now, minutes_add(now(), 90) as 90_minutes_from_now; </dt> <dd> - <indexterm audience="Cloudera">minutes_sub() function</indexterm> + <indexterm audience="hidden">minutes_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of minutes. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1316,7 +1316,7 @@ select now() as right_now, minutes_sub(now(), 90) as 90_minutes_ago; </dt> <dd> - <indexterm audience="Cloudera">month() function</indexterm> + <indexterm audience="hidden">month() function</indexterm> <b>Purpose:</b> Returns the month field, represented as an integer, from the date portion of a <codeph>TIMESTAMP</codeph>. <p> <b>Return type:</b> <codeph>int</codeph> @@ -1342,7 +1342,7 @@ select now() as right_now, month(now()) as current_month; </dt> <dd> - <indexterm audience="Cloudera">months_add() function</indexterm> + <indexterm audience="hidden">months_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of months. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1408,7 +1408,7 @@ with t1 as (select cast('2015-01-31' as timestamp) as jan_31) </dt> <dd> - <indexterm audience="Cloudera">months_between() function</indexterm> + <indexterm audience="hidden">months_between() function</indexterm> <b>Purpose:</b> Returns the number of months between the date portions of two <codeph>TIMESTAMP</codeph> values. Can include a fractional part representing extra days in addition to the full months between the dates. The fractional component is computed by dividing the difference in days by 31 (regardless of the month). @@ -1586,7 +1586,7 @@ select months_between('2015-03-28 23:00:00', '2015-03-01 11:45:00'); </dt> <dd> - <indexterm audience="Cloudera">months_sub() function</indexterm> + <indexterm audience="hidden">months_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of months. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1613,7 +1613,7 @@ with t1 as (select trunc(now(), 'dd') as today) </dt> <dd> - <indexterm audience="Cloudera">nanoseconds_add() function</indexterm> + <indexterm audience="hidden">nanoseconds_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of nanoseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1647,7 +1647,7 @@ select now() as right_now, nanoseconds_add(now(), 1e9) as 1_second_later; </dt> <dd> - <indexterm audience="Cloudera">nanoseconds_sub() function</indexterm> + <indexterm audience="hidden">nanoseconds_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of nanoseconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1679,7 +1679,7 @@ select now() as right_now, nanoseconds_sub(now(), 1e9) as 1_second_earlier; </dt> <dd> - <indexterm audience="Cloudera">now() function</indexterm> + <indexterm audience="hidden">now() function</indexterm> <b>Purpose:</b> Returns the current date and time (in the local time zone) as a <codeph>TIMESTAMP</codeph> value. <p> @@ -1736,7 +1736,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">second() function</indexterm> + <indexterm audience="hidden">second() function</indexterm> <b>Purpose:</b> Returns the second field from a <codeph>TIMESTAMP</codeph> value. <p> <b>Return type:</b> <codeph>int</codeph> @@ -1763,7 +1763,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">seconds_add() function</indexterm> + <indexterm audience="hidden">seconds_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of seconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1790,7 +1790,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">seconds_sub() function</indexterm> + <indexterm audience="hidden">seconds_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of seconds. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -1817,7 +1817,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">subdate() function</indexterm> + <indexterm audience="hidden">subdate() function</indexterm> <b>Purpose:</b> Subtracts a specified number of days from a <codeph>TIMESTAMP</codeph> value. Similar to <codeph>date_sub()</codeph>, but starts with an actual <codeph>TIMESTAMP</codeph> value instead of a string that is converted to a <codeph>TIMESTAMP</codeph>. @@ -1855,7 +1855,7 @@ select now() as right_now, subdate(now(), -15) as now_plus_15; </dt> <dd> - <indexterm audience="Cloudera">timeofday() function</indexterm> + <indexterm audience="hidden">timeofday() function</indexterm> <b>Purpose:</b> Returns a string representation of the current date and time, according to the time of the local system, including any time zone designation. <p> @@ -1921,7 +1921,7 @@ select regexp_replace(timeofday(), '.* ([A-Z]+)$', '\\1') as current_timezone; </dt> <dd> - <indexterm audience="Cloudera">timestamp_cmp() function</indexterm> + <indexterm audience="hidden">timestamp_cmp() function</indexterm> <b>Purpose:</b> Tests if one <codeph>TIMESTAMP</codeph> value is newer than, older than, or identical to another <codeph>TIMESTAMP</codeph> <p> @@ -2015,7 +2015,7 @@ select timestamp_cmp(now(), null) </dt> <dd> - <indexterm audience="Cloudera">to_date() function</indexterm> + <indexterm audience="hidden">to_date() function</indexterm> <b>Purpose:</b> Returns a string representation of the date field from a timestamp value. <p> <b>Return type:</b> <codeph>string</codeph> @@ -2041,7 +2041,7 @@ select now() as right_now, </dt> <dd> - <indexterm audience="Cloudera">to_utc_timestamp() function</indexterm> + <indexterm audience="hidden">to_utc_timestamp() function</indexterm> <b>Purpose:</b> Converts a specified timestamp value in a specified time zone into the corresponding value for the UTC time zone. <p> @@ -2107,7 +2107,7 @@ select now() as 'Current time in California USA', </dt> <dd> - <indexterm audience="Cloudera">trunc() function</indexterm> + <indexterm audience="hidden">trunc() function</indexterm> <b>Purpose:</b> Strips off fields from a <codeph>TIMESTAMP</codeph> value. <p> <b>Unit argument:</b> The <codeph>unit</codeph> argument value is case-sensitive. This argument string @@ -2206,7 +2206,7 @@ select now() + interval 2 weeks as 2_weeks_from_now, </dt> <dd> - <indexterm audience="Cloudera">unix_timestamp() function</indexterm> + <indexterm audience="hidden">unix_timestamp() function</indexterm> <b>Purpose:</b> Returns an integer value representing the current date and time as a delta from the Unix epoch, or converts from a specified date and time value represented as a <codeph>TIMESTAMP</codeph> or <codeph>STRING</codeph>. @@ -2313,7 +2313,7 @@ select unix_timestamp </dt> <dd> - <indexterm audience="Cloudera">weekofyear() function</indexterm> + <indexterm audience="hidden">weekofyear() function</indexterm> <b>Purpose:</b> Returns the corresponding week (1-53) from the date portion of a <codeph>TIMESTAMP</codeph>. <p> <b>Return type:</b> <codeph>int</codeph> @@ -2347,7 +2347,7 @@ select now() + interval 2 weeks as in_2_weeks, </dt> <dd> - <indexterm audience="Cloudera">weeks_add() function</indexterm> + <indexterm audience="hidden">weeks_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of weeks. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -2373,7 +2373,7 @@ select now() as right_now, weeks_add(now(), 2) as week_after_next; </dt> <dd> - <indexterm audience="Cloudera">weeks_sub() function</indexterm> + <indexterm audience="hidden">weeks_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of weeks. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -2398,7 +2398,7 @@ select now() as right_now, weeks_sub(now(), 2) as week_before_last; </dt> <dd> - <indexterm audience="Cloudera">year() function</indexterm> + <indexterm audience="hidden">year() function</indexterm> <b>Purpose:</b> Returns the year field from the date portion of a <codeph>TIMESTAMP</codeph>. <p> <b>Return type:</b> <codeph>int</codeph> @@ -2424,7 +2424,7 @@ select now() as right_now, year(now()) as this_year; </dt> <dd> - <indexterm audience="Cloudera">years_add() function</indexterm> + <indexterm audience="hidden">years_add() function</indexterm> <b>Purpose:</b> Returns the specified date and time plus some number of years. <p> <b>Return type:</b> <codeph>timestamp</codeph> @@ -2464,7 +2464,7 @@ select cast('2016-02-29' as timestamp) as feb_29_2016, </dt> <dd> - <indexterm audience="Cloudera">years_sub() function</indexterm> + <indexterm audience="hidden">years_sub() function</indexterm> <b>Purpose:</b> Returns the specified date and time minus some number of years. <p> <b>Return type:</b> <codeph>timestamp</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_debug_action.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_debug_action.xml b/docs/topics/impala_debug_action.xml index ebb5fa7..72308df 100644 --- a/docs/topics/impala_debug_action.xml +++ b/docs/topics/impala_debug_action.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DEBUG_ACTION query option</indexterm> + <indexterm audience="hidden">DEBUG_ACTION query option</indexterm> Introduces artificial problem conditions within queries. For internal Cloudera debugging and troubleshooting. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_decimal.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_decimal.xml b/docs/topics/impala_decimal.xml index 1be0e2b..0175911 100644 --- a/docs/topics/impala_decimal.xml +++ b/docs/topics/impala_decimal.xml @@ -124,7 +124,7 @@ under the License. if all the digits of the input values were 9s and the absolute values were added together. </p> <!-- Seems like buggy output from this first query, so hiding the example for the time being. --> -<codeblock audience="Cloudera"><![CDATA[[localhost:21000] > select 50000.5 + 12.444, precision(50000.5 + 12.444), scale(50000.5 + 12.444); +<codeblock audience="hidden"><![CDATA[[localhost:21000] > select 50000.5 + 12.444, precision(50000.5 + 12.444), scale(50000.5 + 12.444); +------------------+-----------------------------+-------------------------+ | 50000.5 + 12.444 | precision(50000.5 + 12.444) | scale(50000.5 + 12.444) | +------------------+-----------------------------+-------------------------+ http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_delete.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_delete.xml b/docs/topics/impala_delete.xml index a8be2f7..af20d19 100644 --- a/docs/topics/impala_delete.xml +++ b/docs/topics/impala_delete.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DELETE statement</indexterm> + <indexterm audience="hidden">DELETE statement</indexterm> Deletes one or more rows from a Kudu table. Although deleting a single row or a range of rows would be inefficient for tables using HDFS data files, Kudu is able to perform this operation efficiently. Therefore, this statement http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_describe.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_describe.xml b/docs/topics/impala_describe.xml index b95aa26..2548d44 100644 --- a/docs/topics/impala_describe.xml +++ b/docs/topics/impala_describe.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DESCRIBE statement</indexterm> + <indexterm audience="hidden">DESCRIBE statement</indexterm> The <codeph>DESCRIBE</codeph> statement displays metadata about a table, such as the column names and their data types. <ph rev="2.3.0">In <keyword keyref="impala23_full"/> and higher, you can specify the name of a complex type column, which takes http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_development.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_development.xml b/docs/topics/impala_development.xml index db1859d..41f66c0 100644 --- a/docs/topics/impala_development.xml +++ b/docs/topics/impala_development.xml @@ -175,21 +175,21 @@ under the License. <!-- Bunch of potential concept topics for future consideration. Major areas of Impala modelled on areas of discussion for Oracle Database, and distributed databases in general. --> - <concept id="intro_datatypes" audience="Cloudera"> + <concept id="intro_datatypes" audience="hidden"> <title>Overview of Impala SQL Data Types</title> <conbody/> </concept> - <concept id="intro_network" audience="Cloudera"> + <concept id="intro_network" audience="hidden"> <title>Overview of Impala Network Topology</title> <conbody/> </concept> - <concept id="intro_cluster" audience="Cloudera"> + <concept id="intro_cluster" audience="hidden"> <title>Overview of Impala Cluster Topology</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_cached_reads.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_cached_reads.xml b/docs/topics/impala_disable_cached_reads.xml index 886c645..20391db 100644 --- a/docs/topics/impala_disable_cached_reads.xml +++ b/docs/topics/impala_disable_cached_reads.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DISABLE_CACHED_READS query option</indexterm> + <indexterm audience="hidden">DISABLE_CACHED_READS query option</indexterm> Prevents Impala from reading data files that are <q>pinned</q> in memory through the HDFS caching feature. Primarily a debugging option for cases where processing of HDFS cached data is concentrated on a single http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_codegen.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_codegen.xml b/docs/topics/impala_disable_codegen.xml index 43e5297..82add52 100644 --- a/docs/topics/impala_disable_codegen.xml +++ b/docs/topics/impala_disable_codegen.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DISABLE_CODEGEN query option</indexterm> + <indexterm audience="hidden">DISABLE_CODEGEN query option</indexterm> This is a debug option, intended for diagnosing and working around issues that cause crashes. If a query fails with an <q>illegal instruction</q> or other hardware-specific message, try setting <codeph>DISABLE_CODEGEN=true</codeph> and running the query again. If the query succeeds only when the http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_outermost_topn.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_outermost_topn.xml b/docs/topics/impala_disable_outermost_topn.xml index ebda7ff..2bc1f12 100644 --- a/docs/topics/impala_disable_outermost_topn.xml +++ b/docs/topics/impala_disable_outermost_topn.xml @@ -33,7 +33,7 @@ under the License. <conbody> <p rev="2.5.0"> - <indexterm audience="Cloudera">DISABLE_OUTERMOST_TOPN query option</indexterm> + <indexterm audience="hidden">DISABLE_OUTERMOST_TOPN query option</indexterm> </p> <p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_row_runtime_filtering.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_row_runtime_filtering.xml b/docs/topics/impala_disable_row_runtime_filtering.xml index c12e167..3280084 100644 --- a/docs/topics/impala_disable_row_runtime_filtering.xml +++ b/docs/topics/impala_disable_row_runtime_filtering.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p rev="2.5.0"> - <indexterm audience="Cloudera">DISABLE_ROW_RUNTIME_FILTERING query option</indexterm> + <indexterm audience="hidden">DISABLE_ROW_RUNTIME_FILTERING query option</indexterm> The <codeph>DISABLE_ROW_RUNTIME_FILTERING</codeph> query option reduces the scope of the runtime filtering feature. Queries still dynamically prune partitions, but do not apply the filtering logic to individual rows within partitions. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_streaming_preaggregations.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_streaming_preaggregations.xml b/docs/topics/impala_disable_streaming_preaggregations.xml index e43569d..bde6ec7 100644 --- a/docs/topics/impala_disable_streaming_preaggregations.xml +++ b/docs/topics/impala_disable_streaming_preaggregations.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p rev="2.5.0 IMPALA-1305"> - <indexterm audience="Cloudera">DISABLE_STREAMING_PREAGGREGATIONS query option</indexterm> + <indexterm audience="hidden">DISABLE_STREAMING_PREAGGREGATIONS query option</indexterm> Turns off the <q>streaming preaggregation</q> optimization that is available in <keyword keyref="impala25_full"/> and higher. This optimization reduces unnecessary work performed by queries that perform aggregation operations on columns with few or no duplicate values, for example <codeph>DISTINCT <varname>id_column</varname></codeph> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_disable_unsafe_spills.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_disable_unsafe_spills.xml b/docs/topics/impala_disable_unsafe_spills.xml index d64798a..0a61966 100644 --- a/docs/topics/impala_disable_unsafe_spills.xml +++ b/docs/topics/impala_disable_unsafe_spills.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p rev="2.0.0"> - <indexterm audience="Cloudera">DISABLE_UNSAFE_SPILLS query option</indexterm> + <indexterm audience="hidden">DISABLE_UNSAFE_SPILLS query option</indexterm> Enable this option if you prefer to have queries fail when they exceed the Impala memory limit, rather than write temporary data to disk. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_distinct.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_distinct.xml b/docs/topics/impala_distinct.xml index 63dba1f..710ea0c 100644 --- a/docs/topics/impala_distinct.xml +++ b/docs/topics/impala_distinct.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DISTINCT operator</indexterm> + <indexterm audience="hidden">DISTINCT operator</indexterm> The <codeph>DISTINCT</codeph> operator in a <codeph>SELECT</codeph> statement filters the result set to remove duplicates: </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_data_source.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_data_source.xml b/docs/topics/impala_drop_data_source.xml index 80ebf0d..f4784ea 100644 --- a/docs/topics/impala_drop_data_source.xml +++ b/docs/topics/impala_drop_data_source.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 audience="Cloudera" rev="1.4.0" id="drop_data_source"> +<concept audience="hidden" rev="1.4.0" id="drop_data_source"> <title>DROP DATA SOURCE Statement</title> <titlealts audience="PDF"><navtitle>DROP DATA SOURCE</navtitle></titlealts> @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP DATA SOURCE statement</indexterm> + <indexterm audience="hidden">DROP DATA SOURCE statement</indexterm> </p> <p conref="../shared/impala_common.xml#common/syntax_blurb"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_database.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_database.xml b/docs/topics/impala_drop_database.xml index 78433e6..5dd1536 100644 --- a/docs/topics/impala_drop_database.xml +++ b/docs/topics/impala_drop_database.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP DATABASE statement</indexterm> + <indexterm audience="hidden">DROP DATABASE statement</indexterm> Removes a database from the system. The physical operations involve removing the metadata for the database from the metastore, and deleting the corresponding <codeph>*.db</codeph> directory from HDFS. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_function.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_function.xml b/docs/topics/impala_drop_function.xml index 297741d..6627211 100644 --- a/docs/topics/impala_drop_function.xml +++ b/docs/topics/impala_drop_function.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP FUNCTION statement</indexterm> + <indexterm audience="hidden">DROP FUNCTION statement</indexterm> Removes a user-defined function (UDF), so that it is not available for execution during Impala <codeph>SELECT</codeph> or <codeph>INSERT</codeph> operations. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_role.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_role.xml b/docs/topics/impala_drop_role.xml index 5860391..2a8484b 100644 --- a/docs/topics/impala_drop_role.xml +++ b/docs/topics/impala_drop_role.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP ROLE statement</indexterm> + <indexterm audience="hidden">DROP ROLE statement</indexterm> <!-- Copied from Sentry docs. Turn into conref. I did some rewording for clarity. --> The <codeph>DROP ROLE</codeph> statement removes a role from the metastore database. Once dropped, the role is revoked for all users to whom it was previously assigned, and all privileges granted to that role are http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_stats.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_stats.xml b/docs/topics/impala_drop_stats.xml index 9f54d18..fe5a13e 100644 --- a/docs/topics/impala_drop_stats.xml +++ b/docs/topics/impala_drop_stats.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p rev="2.1.0"> - <indexterm audience="Cloudera">DROP STATS statement</indexterm> + <indexterm audience="hidden">DROP STATS statement</indexterm> Removes the specified statistics from a table or partition. The statistics were originally created by the <codeph>COMPUTE STATS</codeph> or <codeph>COMPUTE INCREMENTAL STATS</codeph> statement. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_table.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_table.xml b/docs/topics/impala_drop_table.xml index 7578ae9..b89368b 100644 --- a/docs/topics/impala_drop_table.xml +++ b/docs/topics/impala_drop_table.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP TABLE statement</indexterm> + <indexterm audience="hidden">DROP TABLE statement</indexterm> Removes an Impala table. Also removes the underlying HDFS data files for internal tables, although not for external tables. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_drop_view.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_drop_view.xml b/docs/topics/impala_drop_view.xml index ba06ee7..bc70cad 100644 --- a/docs/topics/impala_drop_view.xml +++ b/docs/topics/impala_drop_view.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">DROP VIEW statement</indexterm> + <indexterm audience="hidden">DROP VIEW statement</indexterm> Removes the specified view, which was originally created by the <codeph>CREATE VIEW</codeph> statement. Because a view is purely a logical construct (an alias for a query) with no physical data behind it, <codeph>DROP VIEW</codeph> only involves changes to metadata in the metastore database, not any data files in http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_exec_single_node_rows_threshold.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_exec_single_node_rows_threshold.xml b/docs/topics/impala_exec_single_node_rows_threshold.xml index 54ef18d..4822712 100644 --- a/docs/topics/impala_exec_single_node_rows_threshold.xml +++ b/docs/topics/impala_exec_single_node_rows_threshold.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p rev="2.0.0"> - <indexterm audience="Cloudera">EXEC_SINGLE_NODE_ROWS_THRESHOLD query option</indexterm> + <indexterm audience="hidden">EXEC_SINGLE_NODE_ROWS_THRESHOLD query option</indexterm> This setting controls the cutoff point (in terms of number of rows scanned) below which Impala treats a query as a <q>small</q> query, turning off optimizations such as parallel execution and native code generation. The overhead for these optimizations is applicable for queries involving substantial amounts of data, but it http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_explain.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_explain.xml b/docs/topics/impala_explain.xml index 61ea708..4c41fdb 100644 --- a/docs/topics/impala_explain.xml +++ b/docs/topics/impala_explain.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">EXPLAIN statement</indexterm> + <indexterm audience="hidden">EXPLAIN statement</indexterm> Returns the execution plan for a statement, showing the low-level mechanisms that Impala will use to read the data, divide the work among nodes in the cluster, and transmit intermediate and final results across the network. Use <codeph>explain</codeph> followed by a complete <codeph>SELECT</codeph> query. For example: http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_explain_level.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_explain_level.xml b/docs/topics/impala_explain_level.xml index 4d00e4d..ecd06b7 100644 --- a/docs/topics/impala_explain_level.xml +++ b/docs/topics/impala_explain_level.xml @@ -39,7 +39,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">EXPLAIN_LEVEL query option</indexterm> + <indexterm audience="hidden">EXPLAIN_LEVEL query option</indexterm> Controls the amount of detail provided in the output of the <codeph>EXPLAIN</codeph> statement. The basic output can help you identify high-level performance issues such as scanning a higher volume of data or more partitions than you expect. The higher levels of detail show how intermediate results flow between nodes and http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_faq.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_faq.xml b/docs/topics/impala_faq.xml index 6988b8d..6db1b03 100644 --- a/docs/topics/impala_faq.xml +++ b/docs/topics/impala_faq.xml @@ -52,7 +52,7 @@ under the License. FAQs in this category: </p> - <section id="faq_tryout" audience="Cloudera"> + <section id="faq_tryout" audience="hidden"> <title>How do I try Impala out?</title> @@ -73,7 +73,7 @@ under the License. </sectiondiv> </section> - <section id="faq_demo_vm" audience="Cloudera"> + <section id="faq_demo_vm" audience="hidden"> <title>Does Cloudera offer a VM for demonstrating Impala?</title> @@ -473,7 +473,7 @@ through the <codeph>DEFAULT_ORDER_BY_LIMIT</codeph> query option.</ph> information about Impala performance optimizations and tuning techniques for queries. </li> - <li audience="Cloudera"> + <li audience="hidden"> 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. </li> @@ -647,7 +647,7 @@ through the <codeph>DEFAULT_ORDER_BY_LIMIT</codeph> query option.</ph> </sectiondiv> </section> - <section audience="Cloudera" id="faq_roadmap"> + <section audience="hidden" id="faq_roadmap"> <!-- Hidden to avoid RevRec implications. --> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_file_formats.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_file_formats.xml b/docs/topics/impala_file_formats.xml index 3480f15..f68e94f 100644 --- a/docs/topics/impala_file_formats.xml +++ b/docs/topics/impala_file_formats.xml @@ -39,8 +39,8 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">file formats</indexterm> - <indexterm audience="Cloudera">compression</indexterm> + <indexterm audience="hidden">file formats</indexterm> + <indexterm audience="hidden">compression</indexterm> Impala supports several familiar file formats used in Apache Hadoop. Impala can load and query data files produced by other Hadoop components such as Pig or MapReduce, and data files produced by Impala can be used by other components also. The following sections discuss the procedures, limitations, and performance http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_fixed_issues.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_fixed_issues.xml b/docs/topics/impala_fixed_issues.xml index a66f9fb..db4c419 100644 --- a/docs/topics/impala_fixed_issues.xml +++ b/docs/topics/impala_fixed_issues.xml @@ -2003,7 +2003,7 @@ ce601ec : Enable using isilon as the underlying filesystem. fixes to performance and flexibility for dealing with I/O using remote reads. See <xref href="impala_isilon.xml#impala_isilon"/> for details on using Impala and Isilon together. </p> - <p audience="Cloudera"><b>Bug:</b> <xref href="https://jira.cloudera.com/browse/CDH-24040"; scope="external" format="html">CDH-24040</xref></p> + <p audience="hidden"><b>Bug:</b> <xref href="https://jira.cloudera.com/browse/CDH-24040"; scope="external" format="html">CDH-24040</xref></p> <p><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/IMPALA-1968"; scope="external" format="html">IMPALA-1968</xref>, <xref href="https://issues.cloudera.org/browse/IMPALA-1730"; scope="external" format="html">IMPALA-1730</xref></p> </conbody> @@ -2098,7 +2098,7 @@ ce601ec : Enable using isilon as the underlying filesystem. <title>Isilon: fix custom_cluster/test_insert_inherit_permission.py</title> <conbody> <p></p> - <p audience="Cloudera"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> + <p audience="hidden"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> <p><b>Severity:</b> High</p> </conbody> </concept> @@ -2109,7 +2109,7 @@ ce601ec : Enable using isilon as the underlying filesystem. <title>Isilon: add remote HDFS disk queue</title> <conbody> <p></p> - <p audience="Cloudera"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> + <p audience="hidden"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> <p><b>Severity:</b> High</p> </conbody> </concept> @@ -2131,7 +2131,7 @@ ce601ec : Enable using isilon as the underlying filesystem. <title>Isilon: don't warn for multiple remote parquet blocks</title> <conbody> <p></p> - <p audience="Cloudera"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> + <p audience="hidden"><b>Bug:</b> <xref href="https://issues.cloudera.org/browse/"; scope="external" format="html"></xref></p> <p><b>Severity:</b> High</p> </conbody> </concept> @@ -5130,7 +5130,7 @@ Bad stats: key. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-1188"; scope="external" format="html">IMP-1188</xref> </p> @@ -5974,7 +5974,7 @@ hive> NULL</codeblock> Insert INTO TABLE SELECT <constant> will not insert any data and may return an error. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-231"; scope="external" format="html"/> ; KI added 0.1 <i>Cloudera internal only</i> @@ -6436,7 +6436,7 @@ hive> NULL</codeblock> <conbody> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-474"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6551,7 +6551,7 @@ hive> NULL</codeblock> does not propagate to Impala. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-56"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6795,7 +6795,7 @@ hive> NULL</codeblock> impala-shell will incorrectly report that the failed metadata refresh completed successfully. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-611"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6871,7 +6871,7 @@ hive> NULL</codeblock> <conbody> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-601"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6901,7 +6901,7 @@ hive> NULL</codeblock> table will return an <codeph>unknown table</codeph> error message, even if the table is known. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-298"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6925,7 +6925,7 @@ hive> NULL</codeblock> even if the metadata for that table is fixed. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-298"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6947,7 +6947,7 @@ hive> NULL</codeblock> Attempting to select from these tables fails. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-581"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -6970,7 +6970,7 @@ hive> NULL</codeblock> any of the joined tables in the WHERE clause. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-137"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -7002,7 +7002,7 @@ hive> NULL</codeblock> <codeblock>SELECT * FROM (SELECT sum(col1) FROM some_table GROUP BY col1) t1 JOIN other_table ON (...);</codeblock> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-491"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -7026,7 +7026,7 @@ hive> NULL</codeblock> <codeblock>INSERT OVERWRITE TABLE test SELECT * FROM test2 LIMIT 1;</codeblock> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-497"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -7050,7 +7050,7 @@ hive> NULL</codeblock> <codeblock>SELECT * FROM test2 LIMIT 1;</codeblock> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-535"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -7072,7 +7072,7 @@ hive> NULL</codeblock> Attempting to read such files does not generate a diagnostic. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-270"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> @@ -7095,7 +7095,7 @@ hive> NULL</codeblock> exception. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-522"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_grant.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_grant.xml b/docs/topics/impala_grant.xml index 32b08b4..cdba5e0 100644 --- a/docs/topics/impala_grant.xml +++ b/docs/topics/impala_grant.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p rev="2.0.0"> - <indexterm audience="Cloudera">GRANT statement</indexterm> + <indexterm audience="hidden">GRANT statement</indexterm> <!-- Copied from Sentry docs. Turn into conref. I did some rewording for clarity. --> The <codeph>GRANT</codeph> statement grants roles or privileges on specified objects to groups. Only Sentry administrative users can grant roles to a group. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_group_concat.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_group_concat.xml b/docs/topics/impala_group_concat.xml index 0cdeebd..ffa4084 100644 --- a/docs/topics/impala_group_concat.xml +++ b/docs/topics/impala_group_concat.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">group_concat() function</indexterm> + <indexterm audience="hidden">group_concat() function</indexterm> An aggregate function that returns a single string representing the argument value concatenated together for each row of the result set. If the optional separator string is specified, the separator is added between each pair of concatenated values. The default separator is a comma followed by a space. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_hbase.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hbase.xml b/docs/topics/impala_hbase.xml index 6f7daf3..429d828 100644 --- a/docs/topics/impala_hbase.xml +++ b/docs/topics/impala_hbase.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">HBase</indexterm> + <indexterm audience="hidden">HBase</indexterm> You can use Impala to query HBase tables. This capability allows convenient access to a storage system that is tuned for different kinds of workloads than the default with Impala. The default Impala tables use data files stored on HDFS, which are ideal for bulk loads and queries using full-table scans. In contrast, HBase @@ -162,7 +162,7 @@ under the License. </property> </codeblock> - <p audience="Cloudera"> + <p audience="hidden"> 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. @@ -630,7 +630,7 @@ set hbase_caching=1000; </conbody> </concept> - <concept audience="Cloudera" id="hbase_create_new"> + <concept audience="hidden" id="hbase_create_new"> <title>Creating a New HBase Table for Impala to Use</title> @@ -647,7 +647,7 @@ set hbase_caching=1000; </conbody> </concept> - <concept audience="Cloudera" id="hbase_reuse_existing"> + <concept audience="hidden" id="hbase_reuse_existing"> <title>Associate Impala with an Existing HBase Table</title> @@ -664,7 +664,7 @@ set hbase_caching=1000; </conbody> </concept> - <concept audience="Cloudera" id="hbase_column_families"> + <concept audience="hidden" id="hbase_column_families"> <title>Map HBase Columns and Column Families to Impala Columns</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_hbase_cache_blocks.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hbase_cache_blocks.xml b/docs/topics/impala_hbase_cache_blocks.xml index 692d605..5bc3e16 100644 --- a/docs/topics/impala_hbase_cache_blocks.xml +++ b/docs/topics/impala_hbase_cache_blocks.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">HBASE_CACHE_BLOCKS query option</indexterm> + <indexterm audience="hidden">HBASE_CACHE_BLOCKS query option</indexterm> Setting this option is equivalent to calling the <codeph>setCacheBlocks</codeph> method of the class <xref href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html"; http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_hbase_caching.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hbase_caching.xml b/docs/topics/impala_hbase_caching.xml index ae8257f..db0a411 100644 --- a/docs/topics/impala_hbase_caching.xml +++ b/docs/topics/impala_hbase_caching.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">HBASE_CACHING query option</indexterm> + <indexterm audience="hidden">HBASE_CACHING query option</indexterm> Setting this option is equivalent to calling the <codeph>setCaching</codeph> method of the class <xref href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html"; http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_hints.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_hints.xml b/docs/topics/impala_hints.xml index 6430400..7d833f6 100644 --- a/docs/topics/impala_hints.xml +++ b/docs/topics/impala_hints.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">hints</indexterm> + <indexterm audience="hidden">hints</indexterm> The Impala SQL dialect supports query hints, for fine-tuning the inner workings of queries. Specify hints as a temporary workaround for expensive queries, where missing statistics or other factors cause inefficient performance. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_impala_shell.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_impala_shell.xml b/docs/topics/impala_impala_shell.xml index e833c8c..53531a3 100644 --- a/docs/topics/impala_impala_shell.xml +++ b/docs/topics/impala_impala_shell.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">impala-shell</indexterm> + <indexterm audience="hidden">impala-shell</indexterm> You can use the Impala shell tool (<codeph>impala-shell</codeph>) to set up databases and tables, insert data, and issue queries. For ad hoc queries and exploration, you can submit SQL statements in an interactive session. To automate your work, you can specify command-line options to process a single statement or a http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_incompatible_changes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_incompatible_changes.xml b/docs/topics/impala_incompatible_changes.xml index 9fad426..b4cba7a 100644 --- a/docs/topics/impala_incompatible_changes.xml +++ b/docs/topics/impala_incompatible_changes.xml @@ -332,7 +332,7 @@ under the License. <note conref="../shared/impala_common.xml#common/impala_llama_obsolete"/> <ul> - <li rev="IMPALA-2005" audience="Cloudera"> + <li rev="IMPALA-2005" audience="hidden"> <p> If a <codeph>CREATE TABLE AS SELECT</codeph> operation fails while data is being inserted, the table is automatically removed. Previously, the table was left behind with no data. @@ -1276,7 +1276,7 @@ select * from `cross`;</codeblock> to Impala 1.2.x in general. </p> - <p audience="Cloudera" conref="../shared/impala_common.xml#common/cm48_upgrade"/> + <p audience="hidden" conref="../shared/impala_common.xml#common/cm48_upgrade"/> <!-- <note conref="common.xml#common/cdh4_cdh5_upgrade"/> --> </conbody> @@ -1318,7 +1318,7 @@ select * from `cross`;</codeblock> <li/> </ul> - <p audience="Cloudera" conref="../shared/impala_common.xml#common/cm48_upgrade"/> + <p audience="hidden" conref="../shared/impala_common.xml#common/cm48_upgrade"/> <!-- <note conref="common.xml#common/cdh4_cdh5_upgrade"/> --> </conbody> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_insert.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_insert.xml b/docs/topics/impala_insert.xml index 834d946..ed9f78f 100644 --- a/docs/topics/impala_insert.xml +++ b/docs/topics/impala_insert.xml @@ -41,7 +41,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">INSERT statement</indexterm> + <indexterm audience="hidden">INSERT statement</indexterm> Impala supports inserting into tables and partitions that you create with the Impala <codeph>CREATE TABLE</codeph> statement, or pre-defined tables and partitions created through Hive. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_install.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_install.xml b/docs/topics/impala_install.xml index 7daf38d..adb502c 100644 --- a/docs/topics/impala_install.xml +++ b/docs/topics/impala_install.xml @@ -32,15 +32,15 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">installation</indexterm> - <indexterm audience="Cloudera">pseudo-distributed cluster</indexterm> - <indexterm audience="Cloudera">cluster</indexterm> - <indexterm audience="Cloudera">DataNodes</indexterm> - <indexterm audience="Cloudera">NameNode</indexterm> - <indexterm audience="Cloudera">Cloudera Manager</indexterm> - <indexterm audience="Cloudera">impalad</indexterm> - <indexterm audience="Cloudera">impala-shell</indexterm> - <indexterm audience="Cloudera">statestored</indexterm> + <indexterm audience="hidden">installation</indexterm> + <indexterm audience="hidden">pseudo-distributed cluster</indexterm> + <indexterm audience="hidden">cluster</indexterm> + <indexterm audience="hidden">DataNodes</indexterm> + <indexterm audience="hidden">NameNode</indexterm> + <indexterm audience="hidden">Cloudera Manager</indexterm> + <indexterm audience="hidden">impalad</indexterm> + <indexterm audience="hidden">impala-shell</indexterm> + <indexterm audience="hidden">statestored</indexterm> Impala is an open-source add-on to the Cloudera Enterprise Core that returns rapid responses to queries. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_intro.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_intro.xml b/docs/topics/impala_intro.xml index e3b851d..2389537 100644 --- a/docs/topics/impala_intro.xml +++ b/docs/topics/impala_intro.xml @@ -82,7 +82,7 @@ under the License. <conbody> - <p audience="Cloudera" conref="../shared/impala_common.xml#common/impala_overview_diagram"/> + <p audience="hidden" conref="../shared/impala_common.xml#common/impala_overview_diagram"/> <p conref="../shared/impala_common.xml#common/component_list"/> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_invalidate_metadata.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_invalidate_metadata.xml b/docs/topics/impala_invalidate_metadata.xml index 7ec724a..97dfb09 100644 --- a/docs/topics/impala_invalidate_metadata.xml +++ b/docs/topics/impala_invalidate_metadata.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">INVALIDATE METADATA statement</indexterm> + <indexterm audience="hidden">INVALIDATE METADATA statement</indexterm> Marks the metadata for one or all tables as stale. Required after a table is created through the Hive shell, before the table is available for Impala queries. The next time the current Impala node performs a query against a table whose metadata is invalidated, Impala reloads the associated metadata before the query http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_isilon.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_isilon.xml b/docs/topics/impala_isilon.xml index c0459dd..bf93b39 100644 --- a/docs/topics/impala_isilon.xml +++ b/docs/topics/impala_isilon.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Isilon</indexterm> + <indexterm audience="hidden">Isilon</indexterm> You can use Impala to query data files that reside on EMC Isilon storage devices, rather than in HDFS. This capability allows convenient query access to a storage system where you might already be managing large volumes of data. The combination of the Impala query engine and Isilon storage is @@ -102,7 +102,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN); for the <cmdname>impalad</cmdname> daemon on clusters not using Cloudera Manager. </p> - <p audience="Cloudera"> + <p audience="hidden"> <!-- For information about tasks performed on Isilon OneFS, see the information hub for Cloudera on the EMC Community Network: @@ -116,7 +116,7 @@ CREATE TABLE d1.t2 (a TINYINT, b BOOLEAN); <!-- <p outputclass="toc inpage"/> --> </conbody> -<concept id="isilon_cm_configs" audience="Cloudera"> +<concept id="isilon_cm_configs" audience="hidden"> <title>Required Configurations</title> <conbody> <p>Specify the following configurations in Cloudera Manager on the <menucascade><uicontrol>Clusters</uicontrol><uicontrol><varname>Isilon Service</varname></uicontrol><uicontrol>Configuration</uicontrol></menucascade> tab:<ul id="ul_vpx_bw5_vv"> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_jdbc.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_jdbc.xml b/docs/topics/impala_jdbc.xml index 5112e05..62fa285 100644 --- a/docs/topics/impala_jdbc.xml +++ b/docs/topics/impala_jdbc.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">JDBC</indexterm> + <indexterm audience="hidden">JDBC</indexterm> Impala supports the standard JDBC interface, allowing access from commercial Business Intelligence tools and custom software written in Java or other programming languages. The JDBC driver allows you to access Impala from a Java program that you write, or a Business Intelligence or similar tool that uses JDBC to communicate http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_joins.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_joins.xml b/docs/topics/impala_joins.xml index 7ddd829..ef0a67a 100644 --- a/docs/topics/impala_joins.xml +++ b/docs/topics/impala_joins.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">joins</indexterm> + <indexterm audience="hidden">joins</indexterm> A join query is a <codeph>SELECT</codeph> statement that combines data from two or more tables, and returns a result set containing items from some or all of those tables. It is a way to cross-reference and correlate related data that is organized into multiple tables, typically http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_known_issues.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_known_issues.xml b/docs/topics/impala_known_issues.xml index e97290b..72c9b12 100644 --- a/docs/topics/impala_known_issues.xml +++ b/docs/topics/impala_known_issues.xml @@ -412,7 +412,7 @@ https://issues.cloudera.org/browse/IMPALA-2144 - Don't have <!-- To do: Hiding for the moment. https://jira.cloudera.com/browse/CDH-38736 reports the issue is fixed. --> - <concept id="impala-shell_ssl_dependency" audience="Cloudera" rev="impala-shell_ssl_dependency"> + <concept id="impala-shell_ssl_dependency" audience="hidden" rev="impala-shell_ssl_dependency"> <title>impala-shell requires Python with ssl module</title> @@ -572,7 +572,7 @@ impala-shell -s impala --ssl --ca_cert /path_to_truststore/truststore.pem in out-of-memory errors in catalogd and leading to query failures. </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Bug:</b> <xref href="https://jira.cloudera.com/browse/TSB-168"; scope="external" format="html">TSB-168</xref> </p> @@ -1377,7 +1377,7 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE'); table. See <xref href="impala_tables.xml#tables"/> for the differences between internal and external tables. </note> - <p audience="Cloudera"> + <p audience="hidden"> <b>Bug:</b> <xref href="https://issues.cloudera.org/browse/CDH-41605"; scope="external" format="html">CDH-41605</xref> </p> @@ -1397,7 +1397,7 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE'); <conbody> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-469"; scope="external" format="html"/>; KI added 0.1 <i>Cloudera internal only</i> </p> @@ -1427,7 +1427,7 @@ ALTER TABLE table_name SET TBLPROPERTIES('EXTERNAL'='TRUE'); allowed value of type (Hive returns NULL). </p> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Bug:</b> <xref href="https://jira.cloudera.com/browse/IMP-175"; scope="external" format="html">IMPALA-175</xref> ; KI added 0.1 <i>Cloudera internal only</i> </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_kudu.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_kudu.xml b/docs/topics/impala_kudu.xml index 186336b..ef90e63 100644 --- a/docs/topics/impala_kudu.xml +++ b/docs/topics/impala_kudu.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Kudu</indexterm> + <indexterm audience="hidden">Kudu</indexterm> You can use Impala to query Kudu tables. This capability allows convenient access to a storage system that is tuned for different kinds of workloads than the default with Impala. The default Impala tables use data files stored on HDFS, which are ideal for bulk loads and queries using full-table scans. In contrast, Kudu can do http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_langref_unsupported.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_langref_unsupported.xml b/docs/topics/impala_langref_unsupported.xml index 25d995c..f0c326a 100644 --- a/docs/topics/impala_langref_unsupported.xml +++ b/docs/topics/impala_langref_unsupported.xml @@ -35,8 +35,8 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Hive</indexterm> - <indexterm audience="Cloudera">HiveQL</indexterm> + <indexterm audience="hidden">Hive</indexterm> + <indexterm audience="hidden">HiveQL</indexterm> Impala's SQL syntax follows the SQL-92 standard, and includes many industry extensions in areas such as built-in functions. See <xref href="impala_porting.xml#porting"/> for a general discussion of adapting SQL code from a variety of database systems to Impala. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_ldap.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_ldap.xml b/docs/topics/impala_ldap.xml index 3100088..e2f48fa 100644 --- a/docs/topics/impala_ldap.xml +++ b/docs/topics/impala_ldap.xml @@ -189,7 +189,7 @@ under the License. specify the option on the <cmdname>impalad</cmdname> command line. </p> - <p audience="Cloudera"> + <p audience="hidden"> 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>, @@ -303,7 +303,7 @@ username, for example <codeph>[email protected]</codeph>. </metadata> </prolog> <conbody> - <section id="ldap_impala_hue_cm" audience="Cloudera"> + <section id="ldap_impala_hue_cm" audience="hidden"> <title>Enabling LDAP for Impala in Hue Using Cloudera Manager</title> <p> <ol> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_lineage.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_lineage.xml b/docs/topics/impala_lineage.xml index 59c0aa3..b8b76b7 100644 --- a/docs/topics/impala_lineage.xml +++ b/docs/topics/impala_lineage.xml @@ -40,8 +40,8 @@ under the License. <conbody> <p rev="2.2.0"> - <indexterm audience="Cloudera">lineage</indexterm> - <indexterm audience="Cloudera">column lineage</indexterm> + <indexterm audience="hidden">lineage</indexterm> + <indexterm audience="hidden">column lineage</indexterm> <term>Lineage</term> is a feature in the Cloudera Navigator data management component that helps you track where data originated, and how data propagates through the system through SQL statements such as http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_literals.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_literals.xml b/docs/topics/impala_literals.xml index 3d979d6..d0d475c 100644 --- a/docs/topics/impala_literals.xml +++ b/docs/topics/impala_literals.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">literals</indexterm> + <indexterm audience="hidden">literals</indexterm> Each of the Impala data types has corresponding notation for literal values of that type. You specify literal values in SQL statements, such as in the <codeph>SELECT</codeph> list or <codeph>WHERE</codeph> clause of a query, or as an argument to a function call. See <xref href="impala_datatypes.xml#datatypes"/> for a complete @@ -51,7 +51,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">numeric literals</indexterm> + <indexterm audience="hidden">numeric literals</indexterm> To write literals for the integer types (<codeph>TINYINT</codeph>, <codeph>SMALLINT</codeph>, <codeph>INT</codeph>, and <codeph>BIGINT</codeph>), use a sequence of digits with optional leading zeros. </p> @@ -146,7 +146,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">string literals</indexterm> + <indexterm audience="hidden">string literals</indexterm> String literals are quoted using either single or double quotation marks. You can use either kind of quotes for string literals, even both kinds for different literals within the same statement. </p> @@ -320,7 +320,7 @@ select case bool_col when true then 'yes' when false 'no' else 'null' end from t <conbody> <p> - <indexterm audience="Cloudera">NULL</indexterm> + <indexterm audience="hidden">NULL</indexterm> The notion of <codeph>NULL</codeph> values is familiar from all kinds of database systems, but each SQL dialect can have its own behavior and restrictions on <codeph>NULL</codeph> values. For Big Data processing, the precise semantics of <codeph>NULL</codeph> values are significant: any misunderstanding http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_live_progress.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_live_progress.xml b/docs/topics/impala_live_progress.xml index 3f70d86..0c91824 100644 --- a/docs/topics/impala_live_progress.xml +++ b/docs/topics/impala_live_progress.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p rev="2.3.0"> - <indexterm audience="Cloudera">LIVE_PROGRESS query option</indexterm> + <indexterm audience="hidden">LIVE_PROGRESS query option</indexterm> For queries submitted through the <cmdname>impala-shell</cmdname> command, displays an interactive progress bar showing roughly what percentage of processing has been completed. When the query finishes, the progress bar is erased http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_live_summary.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_live_summary.xml b/docs/topics/impala_live_summary.xml index d37877b..94733d2 100644 --- a/docs/topics/impala_live_summary.xml +++ b/docs/topics/impala_live_summary.xml @@ -38,7 +38,7 @@ under the License. <conbody> <p rev="2.3.0"> - <indexterm audience="Cloudera">LIVE_SUMMARY query option</indexterm> + <indexterm audience="hidden">LIVE_SUMMARY query option</indexterm> For queries submitted through the <cmdname>impala-shell</cmdname> command, displays the same output as the <codeph>SUMMARY</codeph> command, with the measurements updated in real time as the query progresses. @@ -142,7 +142,7 @@ LIVE_SUMMARY set to true </codeblock> <!-- Keeping this sample output that illustrates a couple of glitches in the LIVE_SUMMARY display, hidden, to help filing JIRAs. --> -<codeblock audience="Cloudera"><![CDATA[[ +<codeblock audience="hidden"><![CDATA[[ +---------------------+--------+----------+----------+---------+------------+----------+---------------+-----------------------+ | Operator | #Hosts | Avg Time | Max Time | #Rows | Est. #Rows | Peak Mem | Est. Peak Mem | Detail | +---------------------+--------+----------+----------+---------+------------+----------+---------------+-----------------------+ http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_load_data.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_load_data.xml b/docs/topics/impala_load_data.xml index 5442134..8d027f3 100644 --- a/docs/topics/impala_load_data.xml +++ b/docs/topics/impala_load_data.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">LOAD DATA statement</indexterm> + <indexterm audience="hidden">LOAD DATA statement</indexterm> The <codeph>LOAD DATA</codeph> statement streamlines the ETL process for an internal Impala table by moving a data file or all the data files in a directory from an HDFS location into the Impala data directory for that table. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_logging.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_logging.xml b/docs/topics/impala_logging.xml index 40399ef..92b9c88 100644 --- a/docs/topics/impala_logging.xml +++ b/docs/topics/impala_logging.xml @@ -167,7 +167,7 @@ under the License. immediately. </li> - <li audience="Cloudera"> + <li audience="hidden"> Cloudera Manager has an Impala configuration setting that sets the <codeph>-logbuflevel</codeph> startup option. </li> @@ -189,7 +189,7 @@ under the License. <conbody> - <p rev="upstream" audience="Cloudera"><!-- Whole paragraph can probably go. --> + <p rev="upstream" audience="hidden"><!-- 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 file. </p> - <p audience="Cloudera"> + <p audience="hidden"> 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). @@ -459,7 +459,7 @@ I0107 08:42:12.292706 14876 logging.cc:76] Flags (see also /varz are on debug we <conbody> <p> - <indexterm audience="Cloudera">redaction</indexterm> + <indexterm audience="hidden">redaction</indexterm> <term>Log redaction</term> is a security feature that prevents sensitive information from being displayed in locations used by administrators for monitoring and troubleshooting, such as log files, the Cloudera Manager user interface, and the Impala debug web user interface. You configure regular expressions that match
