http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_math_functions.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_math_functions.xml b/docs/topics/impala_math_functions.xml index bfdb91c..d63b0e7 100644 --- a/docs/topics/impala_math_functions.xml +++ b/docs/topics/impala_math_functions.xml @@ -77,7 +77,7 @@ under the License. </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">abs() function</indexterm> + <indexterm audience="hidden">abs() function</indexterm> <b>Purpose:</b> Returns the absolute value of the argument. <p rev="2.0.1" conref="../shared/impala_common.xml#common/return_type_same"/> <p> @@ -96,7 +96,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">acos() function</indexterm> + <indexterm audience="hidden">acos() function</indexterm> <b>Purpose:</b> Returns the arccosine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -112,7 +112,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">asin() function</indexterm> + <indexterm audience="hidden">asin() function</indexterm> <b>Purpose:</b> Returns the arcsine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -128,7 +128,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">atan() function</indexterm> + <indexterm audience="hidden">atan() function</indexterm> <b>Purpose:</b> Returns the arctangent of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -144,7 +144,7 @@ under the License. </dt> <dd rev="2.3.0 IMPALA-1771"> - <indexterm audience="Cloudera">atan2() function</indexterm> + <indexterm audience="hidden">atan2() function</indexterm> <b>Purpose:</b> Returns the arctangent of the two arguments, with the signs of the arguments used to determine the quadrant of the result. <p> @@ -161,7 +161,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">bin() function</indexterm> + <indexterm audience="hidden">bin() function</indexterm> <b>Purpose:</b> Returns the binary representation of an integer value, that is, a string of 0 and 1 digits. <p> @@ -183,7 +183,7 @@ under the License. </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">ceil() function</indexterm> + <indexterm audience="hidden">ceil() function</indexterm> <b>Purpose:</b> Returns the smallest integer that is greater than or equal to the argument. <p> <b>Return type:</b> <codeph>int</codeph> or <codeph>decimal(p,s)</codeph> depending on the type of the @@ -201,7 +201,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">conv() function</indexterm> + <indexterm audience="hidden">conv() function</indexterm> <b>Purpose:</b> Returns a string representation of an integer value in a particular base. The input value can be a string, for example to convert a hexadecimal number such as <codeph>fce2</codeph> to decimal. To use the return value as a number (for example, when converting to base 10), use <codeph>CAST()</codeph> @@ -220,7 +220,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">cos() function</indexterm> + <indexterm audience="hidden">cos() function</indexterm> <b>Purpose:</b> Returns the cosine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -236,7 +236,7 @@ under the License. </dt> <dd rev="2.3.0 IMPALA-1771"> - <indexterm audience="Cloudera">cosh() function</indexterm> + <indexterm audience="hidden">cosh() function</indexterm> <b>Purpose:</b> Returns the hyperbolic cosine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -252,7 +252,7 @@ under the License. </dt> <dd rev="2.3.0 IMPALA-1771"> - <indexterm audience="Cloudera">cot() function</indexterm> + <indexterm audience="hidden">cot() function</indexterm> <b>Purpose:</b> Returns the cotangent of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -269,7 +269,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">degrees() function</indexterm> + <indexterm audience="hidden">degrees() function</indexterm> <b>Purpose:</b> Converts argument value from radians to degrees. <p> <b>Return type:</b> <codeph>double</codeph> @@ -285,7 +285,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">e() function</indexterm> + <indexterm audience="hidden">e() function</indexterm> <b>Purpose:</b> Returns the <xref href="https://en.wikipedia.org/wiki/E_(mathematical_constant" scope="external" format="html">mathematical constant e</xref>. @@ -304,7 +304,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">exp() function</indexterm> + <indexterm audience="hidden">exp() function</indexterm> <b>Purpose:</b> Returns the <xref href="https://en.wikipedia.org/wiki/E_(mathematical_constant" scope="external" format="html">mathematical constant e</xref> raised to the power of the argument. @@ -321,7 +321,7 @@ under the License. <codeph>factorial(integer_type a)</codeph> </dt> <dd rev="2.3.0"> - <indexterm audience="Cloudera">factorial() function</indexterm> + <indexterm audience="hidden">factorial() function</indexterm> <b>Purpose:</b> Computes the <xref href="https://en.wikipedia.org/wiki/Factorial"; scope="external" format="html">factorial</xref> of an integer value. It works with any integer type. <p conref="../shared/impala_common.xml#common/added_in_230"/> @@ -377,7 +377,7 @@ select factorial(-100); </dt> <dd> - <indexterm audience="Cloudera">floor() function</indexterm> + <indexterm audience="hidden">floor() function</indexterm> <b>Purpose:</b> Returns the largest integer that is less than or equal to the argument. <p> <b>Return type:</b> <codeph>bigint</codeph> or <codeph>decimal(p,s)</codeph> depending on the type of @@ -394,7 +394,7 @@ select factorial(-100); </dt> <dd> - <indexterm audience="Cloudera">fmod() function</indexterm> + <indexterm audience="hidden">fmod() function</indexterm> <b>Purpose:</b> Returns the modulus of a floating-point number. Equivalent to the <codeph>%</codeph> arithmetic operator. <p> <b>Return type:</b> <codeph>float</codeph> or <codeph>double</codeph>, depending on type of arguments @@ -477,7 +477,7 @@ select fmod(9.9,3.3); </dt> <dd rev="1.2.2"> - <indexterm audience="Cloudera">fnv_hash() function</indexterm> + <indexterm audience="hidden">fnv_hash() function</indexterm> <b>Purpose:</b> Returns a consistent 64-bit value derived from the input argument, for convenience of implementing hashing logic in an application. <p> @@ -567,7 +567,7 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">greatest() function</indexterm> + <indexterm audience="hidden">greatest() function</indexterm> <b>Purpose:</b> Returns the largest value from a list of expressions. <p conref="../shared/impala_common.xml#common/return_same_type"/> </dd> @@ -581,7 +581,7 @@ select fmod(9.9,3.3); </dt> <dd> - <indexterm audience="Cloudera">hex() function</indexterm> + <indexterm audience="hidden">hex() function</indexterm> <b>Purpose:</b> Returns the hexadecimal representation of an integer value, or of the characters in a string. <p> @@ -598,7 +598,7 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">is_inf() function</indexterm> + <indexterm audience="hidden">is_inf() function</indexterm> <b>Purpose:</b> Tests whether a value is equal to the special value <q>inf</q>, signifying infinity. <p> <b>Return type:</b> <codeph>boolean</codeph> @@ -616,7 +616,7 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">is_nan() function</indexterm> + <indexterm audience="hidden">is_nan() function</indexterm> <b>Purpose:</b> Tests whether a value is equal to the special value <q>NaN</q>, signifying <q>not a number</q>. <p> @@ -637,7 +637,7 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">least() function</indexterm> + <indexterm audience="hidden">least() function</indexterm> <b>Purpose:</b> Returns the smallest value from a list of expressions. <p conref="../shared/impala_common.xml#common/return_same_type"/> </dd> @@ -652,8 +652,8 @@ select fmod(9.9,3.3); </dt> <dd> - <indexterm audience="Cloudera">ln() function</indexterm> - <indexterm audience="Cloudera">dlog1() function</indexterm> + <indexterm audience="hidden">ln() function</indexterm> + <indexterm audience="hidden">dlog1() function</indexterm> <b>Purpose:</b> Returns the <xref href="https://en.wikipedia.org/wiki/Natural_logarithm"; scope="external" format="html">natural logarithm</xref> of the argument. @@ -671,7 +671,7 @@ select fmod(9.9,3.3); </dt> <dd> - <indexterm audience="Cloudera">log() function</indexterm> + <indexterm audience="hidden">log() function</indexterm> <b>Purpose:</b> Returns the logarithm of the second argument to the specified base. <p> <b>Return type:</b> <codeph>double</codeph> @@ -688,8 +688,8 @@ select fmod(9.9,3.3); </dt> <dd> - <indexterm audience="Cloudera">log10() function</indexterm> - <indexterm audience="Cloudera">dlog10() function</indexterm> + <indexterm audience="hidden">log10() function</indexterm> + <indexterm audience="hidden">dlog10() function</indexterm> <b>Purpose:</b> Returns the logarithm of the argument to the base 10. <p> <b>Return type:</b> <codeph>double</codeph> @@ -705,7 +705,7 @@ select fmod(9.9,3.3); </dt> <dd> - <indexterm audience="Cloudera">log2() function</indexterm> + <indexterm audience="hidden">log2() function</indexterm> <b>Purpose:</b> Returns the logarithm of the argument to the base 2. <p> <b>Return type:</b> <codeph>double</codeph> @@ -722,10 +722,10 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">max_int() function</indexterm> - <indexterm audience="Cloudera">max_tinyint() function</indexterm> - <indexterm audience="Cloudera">max_smallint() function</indexterm> - <indexterm audience="Cloudera">max_bigint() function</indexterm> + <indexterm audience="hidden">max_int() function</indexterm> + <indexterm audience="hidden">max_tinyint() function</indexterm> + <indexterm audience="hidden">max_smallint() function</indexterm> + <indexterm audience="hidden">max_bigint() function</indexterm> <b>Purpose:</b> Returns the largest value of the associated integral type. <p> <b>Return type:</b> The same as the integral type being checked. @@ -749,10 +749,10 @@ select fmod(9.9,3.3); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">min_int() function</indexterm> - <indexterm audience="Cloudera">min_tinyint() function</indexterm> - <indexterm audience="Cloudera">min_smallint() function</indexterm> - <indexterm audience="Cloudera">min_bigint() function</indexterm> + <indexterm audience="hidden">min_int() function</indexterm> + <indexterm audience="hidden">min_tinyint() function</indexterm> + <indexterm audience="hidden">min_smallint() function</indexterm> + <indexterm audience="hidden">min_bigint() function</indexterm> <b>Purpose:</b> Returns the smallest value of the associated integral type (a negative number). <p> <b>Return type:</b> The same as the integral type being checked. @@ -774,7 +774,7 @@ select fmod(9.9,3.3); </dt> <dd rev="2.2.0"> - <indexterm audience="Cloudera">mod() function</indexterm> + <indexterm audience="hidden">mod() function</indexterm> <b>Purpose:</b> Returns the modulus of a number. Equivalent to the <codeph>%</codeph> arithmetic operator. Works with any size integer type, any size floating-point type, and <codeph>DECIMAL</codeph> with any precision and scale. @@ -867,7 +867,7 @@ select mod(9.9,3.0); </dt> <dd> - <indexterm audience="Cloudera">negative() function</indexterm> + <indexterm audience="hidden">negative() function</indexterm> <b>Purpose:</b> Returns the argument with the sign reversed; returns a positive value if the argument was already negative. <p rev="2.0.1" conref="../shared/impala_common.xml#common/return_type_same"/> @@ -892,7 +892,7 @@ select mod(9.9,3.0); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">pi() function</indexterm> + <indexterm audience="hidden">pi() function</indexterm> <b>Purpose:</b> Returns the constant pi. <p> <b>Return type:</b> <codeph>double</codeph> @@ -908,7 +908,7 @@ select mod(9.9,3.0); </dt> <dd> - <indexterm audience="Cloudera">pmod() function</indexterm> + <indexterm audience="hidden">pmod() function</indexterm> <b>Purpose:</b> Returns the positive modulus of a number. Primarily for <xref href="https://issues.apache.org/jira/browse/HIVE-656"; scope="external" format="html">HiveQL compatibility</xref>. <p> @@ -974,7 +974,7 @@ select pmod(5,-2); </dt> <dd> - <indexterm audience="Cloudera">positive() function</indexterm> + <indexterm audience="hidden">positive() function</indexterm> <b>Purpose:</b> Returns the original argument unchanged (even if the argument is negative). <p rev="2.0.1" conref="../shared/impala_common.xml#common/return_type_same"/> <!-- @@ -1001,10 +1001,10 @@ select pmod(5,-2); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">pow() function</indexterm> - <indexterm audience="Cloudera">power() function</indexterm> - <indexterm audience="Cloudera">dpow() function</indexterm> - <indexterm audience="Cloudera">fpow() function</indexterm> + <indexterm audience="hidden">pow() function</indexterm> + <indexterm audience="hidden">power() function</indexterm> + <indexterm audience="hidden">dpow() function</indexterm> + <indexterm audience="hidden">fpow() function</indexterm> <b>Purpose:</b> Returns the first argument raised to the power of the second argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1020,7 +1020,7 @@ select pmod(5,-2); </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">precision() function</indexterm> + <indexterm audience="hidden">precision() function</indexterm> <b>Purpose:</b> Computes the precision (number of decimal digits) needed to represent the type of the argument expression as a <codeph>DECIMAL</codeph> value. <p conref="../shared/impala_common.xml#common/usage_notes_blurb"/> @@ -1045,7 +1045,7 @@ select pmod(5,-2); </dt> <dd> - <indexterm audience="Cloudera">quotient() function</indexterm> + <indexterm audience="hidden">quotient() function</indexterm> <b>Purpose:</b> Returns the first argument divided by the second argument, discarding any fractional part. Avoids promoting arguments to <codeph>DOUBLE</codeph> as happens with the <codeph>/</codeph> SQL operator. @@ -1063,7 +1063,7 @@ select pmod(5,-2); </dt> <dd> - <indexterm audience="Cloudera">radians() function</indexterm> + <indexterm audience="hidden">radians() function</indexterm> <b>Purpose:</b> Converts argument value from degrees to radians. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1081,7 +1081,7 @@ select pmod(5,-2); </dt> <dd> - <indexterm audience="Cloudera">rand() function</indexterm> + <indexterm audience="hidden">rand() function</indexterm> <b>Purpose:</b> Returns a random value between 0 and 1. After <codeph>rand()</codeph> is called with a seed argument, it produces a consistent random sequence based on the seed value. <p> @@ -1179,8 +1179,8 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd> - <indexterm audience="Cloudera">round() function</indexterm> - <indexterm audience="Cloudera">dround() function</indexterm> + <indexterm audience="hidden">round() function</indexterm> + <indexterm audience="hidden">dround() function</indexterm> <b>Purpose:</b> Rounds a floating-point value. By default (with a single argument), rounds to the nearest integer. Values ending in .5 are rounded up for positive numbers, down for negative numbers (that is, away from zero). The optional second argument specifies how many digits to leave after the decimal point; @@ -1204,7 +1204,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd rev="1.4.0"> - <indexterm audience="Cloudera">scale() function</indexterm> + <indexterm audience="hidden">scale() function</indexterm> <b>Purpose:</b> Computes the scale (number of decimal digits to the right of the decimal point) needed to represent the type of the argument expression as a <codeph>DECIMAL</codeph> value. <p conref="../shared/impala_common.xml#common/usage_notes_blurb"/> @@ -1229,7 +1229,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd> - <indexterm audience="Cloudera">sign() function</indexterm> + <indexterm audience="hidden">sign() function</indexterm> <b>Purpose:</b> Returns -1, 0, or 1 to indicate the signedness of the argument value. <p> <b>Return type:</b> <codeph>int</codeph> @@ -1245,7 +1245,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd> - <indexterm audience="Cloudera">sin() function</indexterm> + <indexterm audience="hidden">sin() function</indexterm> <b>Purpose:</b> Returns the sine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1261,7 +1261,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd rev="2.3.0 IMPALA-1771"> - <indexterm audience="Cloudera">sinh() function</indexterm> + <indexterm audience="hidden">sinh() function</indexterm> <b>Purpose:</b> Returns the hyperbolic sine of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1278,8 +1278,8 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd> - <indexterm audience="Cloudera">sqrt() function</indexterm> - <indexterm audience="Cloudera">dsqrt() function</indexterm> + <indexterm audience="hidden">sqrt() function</indexterm> + <indexterm audience="hidden">dsqrt() function</indexterm> <b>Purpose:</b> Returns the square root of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1295,7 +1295,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd> - <indexterm audience="Cloudera">tan() function</indexterm> + <indexterm audience="hidden">tan() function</indexterm> <b>Purpose:</b> Returns the tangent of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1311,7 +1311,7 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd rev="2.3.0 IMPALA-1771"> - <indexterm audience="Cloudera">tanh() function</indexterm> + <indexterm audience="hidden">tanh() function</indexterm> <b>Purpose:</b> Returns the hyperbolic tangent of the argument. <p> <b>Return type:</b> <codeph>double</codeph> @@ -1328,8 +1328,8 @@ select x, unix_timestamp(now()), rand(unix_timestamp(now())) </dt> <dd rev="2.3.0"> - <indexterm audience="Cloudera">truncate() function</indexterm> - <indexterm audience="Cloudera">dtrunc() function</indexterm> + <indexterm audience="hidden">truncate() function</indexterm> + <indexterm audience="hidden">dtrunc() function</indexterm> <b>Purpose:</b> Removes some or all fractional digits from a numeric value. With no argument, removes all fractional digits, leaving an integer value. The optional argument specifies the number of fractional digits to include @@ -1393,7 +1393,7 @@ select truncate(3.456,7) </dt> <dd> - <indexterm audience="Cloudera">unhex() function</indexterm> + <indexterm audience="hidden">unhex() function</indexterm> <b>Purpose:</b> Returns a string of characters with ASCII values corresponding to pairs of hexadecimal digits in the argument. <p>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_max.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_max.xml b/docs/topics/impala_max.xml index 1e291f7..5cebf0d 100644 --- a/docs/topics/impala_max.xml +++ b/docs/topics/impala_max.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">max() function</indexterm> + <indexterm audience="hidden">max() function</indexterm> An aggregate function that returns the maximum value from a set of numbers. Opposite of the <codeph>MIN</codeph> function. Its single argument can be numeric column, or the numeric result of a function or expression applied to the column value. Rows with a <codeph>NULL</codeph> value for the specified column http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_max_block_mgr_memory.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_max_block_mgr_memory.xml b/docs/topics/impala_max_block_mgr_memory.xml index 2bf4061..c66b89c 100644 --- a/docs/topics/impala_max_block_mgr_memory.xml +++ b/docs/topics/impala_max_block_mgr_memory.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p rev="2.1.0"> - <indexterm audience="Cloudera">MAX_BLOCK_MGR_MEMORY query option</indexterm> + <indexterm audience="hidden">MAX_BLOCK_MGR_MEMORY query option</indexterm> </p> <p></p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_max_errors.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_max_errors.xml b/docs/topics/impala_max_errors.xml index cb70bc9..63bae5b 100644 --- a/docs/topics/impala_max_errors.xml +++ b/docs/topics/impala_max_errors.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">MAX_ERRORS query option</indexterm> + <indexterm audience="hidden">MAX_ERRORS query option</indexterm> Maximum number of non-fatal errors for any particular query that are recorded in the Impala log file. For example, if a billion-row table had a non-fatal data error in every row, you could diagnose the problem without all billion errors being logged. Unspecified or 0 indicates the built-in default value of 1000. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_max_num_runtime_filters.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_max_num_runtime_filters.xml b/docs/topics/impala_max_num_runtime_filters.xml index c50fadf..7ac06ee 100644 --- a/docs/topics/impala_max_num_runtime_filters.xml +++ b/docs/topics/impala_max_num_runtime_filters.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p rev="2.5.0"> - <indexterm audience="Cloudera">MAX_NUM_RUNTIME_FILTERS query option</indexterm> + <indexterm audience="hidden">MAX_NUM_RUNTIME_FILTERS query option</indexterm> The <codeph>MAX_NUM_RUNTIME_FILTERS</codeph> query option sets an upper limit on the number of runtime filters that can be produced for each query. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_max_scan_range_length.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_max_scan_range_length.xml b/docs/topics/impala_max_scan_range_length.xml index a828e45..3fbd4ca 100644 --- a/docs/topics/impala_max_scan_range_length.xml +++ b/docs/topics/impala_max_scan_range_length.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">MAX_SCAN_RANGE_LENGTH query option</indexterm> + <indexterm audience="hidden">MAX_SCAN_RANGE_LENGTH query option</indexterm> Maximum length of the scan range. Interacts with the number of HDFS blocks in the table to determine how many CPU cores across the cluster are involved with the processing for a query. (Each core processes one scan range.) http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_mem_limit.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_mem_limit.xml b/docs/topics/impala_mem_limit.xml index ca0f2aa..98bc470 100644 --- a/docs/topics/impala_mem_limit.xml +++ b/docs/topics/impala_mem_limit.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">MEM_LIMIT query option</indexterm> + <indexterm audience="hidden">MEM_LIMIT query option</indexterm> When resource management is not enabled, defines the maximum amount of memory a query can allocate on each node. Therefore, the total memory that can be used by a query is the <codeph>MEM_LIMIT</codeph> times the number of nodes. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_min.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_min.xml b/docs/topics/impala_min.xml index 8c242e3..f85ac62 100644 --- a/docs/topics/impala_min.xml +++ b/docs/topics/impala_min.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">min() function</indexterm> + <indexterm audience="hidden">min() function</indexterm> An aggregate function that returns the minimum value from a set of numbers. Opposite of the <codeph>MAX</codeph> function. Its single argument can be numeric column, or the numeric result of a function or expression applied to the column value. Rows with a <codeph>NULL</codeph> value for the specified column http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_misc_functions.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_misc_functions.xml b/docs/topics/impala_misc_functions.xml index 15ecaa8..c5ca9eb 100644 --- a/docs/topics/impala_misc_functions.xml +++ b/docs/topics/impala_misc_functions.xml @@ -47,7 +47,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">current_database() function</indexterm> + <indexterm audience="hidden">current_database() function</indexterm> <b>Purpose:</b> Returns the database that the session is currently using, either <codeph>default</codeph> if no database has been selected, or whatever database the session switched to through a <codeph>USE</codeph> statement or the <cmdname>impalad</cmdname><codeph>-d</codeph> option. @@ -65,7 +65,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">effective_user() function</indexterm> + <indexterm audience="hidden">effective_user() function</indexterm> <b>Purpose:</b> Typically returns the same value as <codeph>user()</codeph>, except if delegation is enabled, in which case it returns the ID of the delegated user. <p> @@ -85,7 +85,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">pid() function</indexterm> + <indexterm audience="hidden">pid() function</indexterm> <b>Purpose:</b> Returns the process ID of the <cmdname>impalad</cmdname> daemon that the session is connected to. You can use it during low-level debugging, to issue Linux commands that trace, show the arguments, and so on the <cmdname>impalad</cmdname> process. @@ -96,14 +96,14 @@ under the License. </dlentry> - <dlentry audience="Cloudera" id="sleep"> + <dlentry audience="hidden" id="sleep"> <dt> <codeph>sleep(int ms)</codeph> </dt> <dd> - <indexterm audience="Cloudera">sleep() function</indexterm> + <indexterm audience="hidden">sleep() function</indexterm> <b>Purpose:</b> Pauses the query for a specified number of milliseconds. For slowing down queries with small result sets enough to monitor runtime execution, memory usage, or other factors that otherwise would be difficult to capture during the brief interval of query execution. When used in the @@ -126,7 +126,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">user() function</indexterm> + <indexterm audience="hidden">user() function</indexterm> <b>Purpose:</b> Returns the username of the Linux user who is connected to the <cmdname>impalad</cmdname> daemon. Typically called a single time, in a query without any <codeph>FROM</codeph> clause, to understand how authorization settings apply in a security context; once you know the logged-in username, @@ -150,7 +150,7 @@ under the License. </dt> <dd> - <indexterm audience="Cloudera">uuid() function</indexterm> + <indexterm audience="hidden">uuid() function</indexterm> <b>Purpose:</b> Returns a <xref href="https://en.wikipedia.org/wiki/Universally_unique_identifier"; scope="external" format="html">universal unique identifier</xref>, a 128-bit value encoded as a string with groups of hexadecimal digits separated by dashes. <p> <b>Return type:</b> <codeph>string</codeph> @@ -198,7 +198,7 @@ select uuid() from four_row_table; </dt> <dd> - <indexterm audience="Cloudera">version() function</indexterm> + <indexterm audience="hidden">version() function</indexterm> <b>Purpose:</b> Returns information such as the precise version number and build date for the <codeph>impalad</codeph> daemon that you are currently connected to. Typically used to confirm that you are connected to the expected level of Impala to use a particular feature, or to connect to several nodes http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_ndv.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_ndv.xml b/docs/topics/impala_ndv.xml index f1bff69..0cc5443 100644 --- a/docs/topics/impala_ndv.xml +++ b/docs/topics/impala_ndv.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">ndv() function</indexterm> + <indexterm audience="hidden">ndv() function</indexterm> An aggregate function that returns an approximate value similar to the result of <codeph>COUNT(DISTINCT <varname>col</varname>)</codeph>, the <q>number of distinct values</q>. It is much faster than the combination of <codeph>COUNT</codeph> and <codeph>DISTINCT</codeph>, and uses a constant amount of memory and http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_new_features.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_new_features.xml b/docs/topics/impala_new_features.xml index 8c532d0..5c8405d 100644 --- a/docs/topics/impala_new_features.xml +++ b/docs/topics/impala_new_features.xml @@ -95,7 +95,7 @@ under the License. </li> </ul> </li> - <li audience="Cloudera"> + <li audience="hidden"> <p rev="IMPALA-3210 CDH-43736"><!-- Patch didn't make it into in <keyword keyref="impala27_full"/> --> [<xref href="https://issues.cloudera.org/browse/IMPALA-3210"; scope="external" format="html">IMPALA-3210</xref>] The analytic functions <codeph>FIRST_VALUE()</codeph> and <codeph>LAST_VALUE()</codeph> @@ -171,7 +171,7 @@ under the License. column definitions in Avro tables. </p> </li> - <li audience="Cloudera"><!-- Patch didn't make it into in <keyword keyref="impala27_full"/> --> + <li audience="hidden"><!-- Patch didn't make it into in <keyword keyref="impala27_full"/> --> <p rev="IMPALA-1654 CDH-43747"> [<xref href="https://issues.cloudera.org/browse/IMPALA-1654"; scope="external" format="html">IMPALA-1654</xref>] Several kinds of DDL operations @@ -934,21 +934,21 @@ under the License. <ph audience="PDF">See <xref href="impala_optimize_partition_key_scans.xml"/> for details.</ph> </p> </li> - <li audience="Cloudera"><!-- All the other undocumented query options are not really new features for this release, so hiding this whole bullet. --> + <li audience="hidden"><!-- All the other undocumented query options are not really new features for this release, so hiding this whole bullet. --> <p> Other new query options: </p> <ul> - <li audience="Cloudera"><!-- Actually from a long way back, just never documented. Not sure if appropriate to keep internal-only or expose. --> + <li audience="hidden"><!-- Actually from a long way back, just never documented. Not sure if appropriate to keep internal-only or expose. --> <codeph>DISABLE_OUTERMOST_TOPN</codeph> </li> - <li audience="Cloudera"><!-- Actually from a long way back, just never documented. Not sure if appropriate to keep internal-only or expose. --> + <li audience="hidden"><!-- Actually from a long way back, just never documented. Not sure if appropriate to keep internal-only or expose. --> <codeph>RM_INITIAL_MEM</codeph> </li> - <li audience="Cloudera"><!-- Seems to be related to writing sequence files, a capability not externalized at this time. --> + <li audience="hidden"><!-- Seems to be related to writing sequence files, a capability not externalized at this time. --> <codeph>SEQ_COMPRESSION_MODE</codeph> </li> - <li audience="Cloudera"><!-- Actually, was only used for working around one JIRA. Being deprecated now in Impala 2.3 via IMPALA-2963. --> + <li audience="hidden"><!-- Actually, was only used for working around one JIRA. Being deprecated now in Impala 2.3 via IMPALA-2963. --> <codeph>DISABLE_CACHED_READS</codeph> </li> </ul> @@ -1444,7 +1444,7 @@ under the License. </concept> - <concept audience="Cloudera" rev="5.4.6" id="new_features_226"> + <concept audience="hidden" rev="5.4.6" id="new_features_226"> <title>New Features in Impala 2.2.6 / CDH 5.4.6</title> @@ -1500,7 +1500,7 @@ under the License. <!-- I let the 5.4.3/5.4.3 subtopic above remain in existence, but now back to hiding specific 5.4.x subtopics after the .0 one that has the actual new features. - <concept audience="Cloudera" rev="5.4.2" id="new_features_222"> + <concept audience="hidden" rev="5.4.2" id="new_features_222"> <title>New Features in Impala 2.2.x for CDH 5.4.2</title> @@ -2130,7 +2130,7 @@ under the License. values are padded with spaces on the right. See <xref href="impala_char.xml#char"/> for details. </li> - <li audience="Cloudera"> + <li audience="hidden"> <!-- This feature will be undocumented in Impala 2.0, probably ready for prime time in 2.1. --> <codeph>DATE</codeph>. See <xref href="impala_date.xml#date"/> for details. </li> @@ -2311,7 +2311,7 @@ under the License. </p> </li> - <li audience="Cloudera"> + <li audience="hidden"> <!-- This feature will be undocumented in Impala 2.0, probably ready for prime time in 2.1. --> <p> Improved file format support. Impala can now write to Avro, compressed text, SequenceFile, and RCFile @@ -2338,7 +2338,7 @@ under the License. </p> </li> - <li audience="Cloudera"> + <li audience="hidden"> <!-- This feature will be undocumented in Impala 2.0, probably ready for prime time in 2.1. --> <p> The <codeph>COMPUTE STATS</codeph> statement can now gather statistics for newly added partitions @@ -2579,7 +2579,7 @@ under the License. </p> </li> - <li audience="Cloudera"> + <li audience="hidden"> <!-- Not documenting for 1.4. Revisit in a future release. --> <p> Data sources. <ph audience="PDF">See <xref href="impala_data_sources.xml#data_sources"/> for @@ -2630,7 +2630,7 @@ under the License. <ul> <!-- This particular change has been pushed out to a later release. --> - <li audience="Cloudera"> + <li audience="hidden"> Certain simple aggregation operations (with no <codeph>GROUP BY</codeph> step) are multi-threaded if spare cores are available. </li> @@ -3266,7 +3266,7 @@ under the License. </p> </li> - <li audience="Cloudera"> + <li audience="hidden"> <p> Integration with the YARN resource management framework. Only available in combination with CDH 5. This feature makes use of the underlying YARN service, plus an additional service (Llama) that coordinates http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_num_nodes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_num_nodes.xml b/docs/topics/impala_num_nodes.xml index 44c1eb8..f885124 100644 --- a/docs/topics/impala_num_nodes.xml +++ b/docs/topics/impala_num_nodes.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">NUM_NODES query option</indexterm> + <indexterm audience="hidden">NUM_NODES query option</indexterm> Limit the number of nodes that process a query, typically during debugging. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_num_scanner_threads.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_num_scanner_threads.xml b/docs/topics/impala_num_scanner_threads.xml index c12f672..b7a47ae 100644 --- a/docs/topics/impala_num_scanner_threads.xml +++ b/docs/topics/impala_num_scanner_threads.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">NUM_SCANNER_THREADS query option</indexterm> + <indexterm audience="hidden">NUM_SCANNER_THREADS query option</indexterm> Maximum number of scanner threads (on each node) used for each query. By default, Impala uses as many cores as are available (one thread per core). You might lower this value if queries are using excessive resources on a busy cluster. Impala imposes a maximum value automatically, so a high value has no practical effect. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_odbc.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_odbc.xml b/docs/topics/impala_odbc.xml index c819a6d..402bc11 100644 --- a/docs/topics/impala_odbc.xml +++ b/docs/topics/impala_odbc.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">ODBC</indexterm> + <indexterm audience="hidden">ODBC</indexterm> Third-party products can be designed to integrate with Impala using ODBC. For the best experience, ensure any third-party product you intend to use is supported. Verifying support includes checking that the versions of Impala, ODBC, the operating system, and the third-party product have all been approved for use together. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_operators.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_operators.xml b/docs/topics/impala_operators.xml index dd916ff..2a944ce 100644 --- a/docs/topics/impala_operators.xml +++ b/docs/topics/impala_operators.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">operators</indexterm> + <indexterm audience="hidden">operators</indexterm> SQL operators are a class of comparison functions that are widely used within the <codeph>WHERE</codeph> clauses of <codeph>SELECT</codeph> statements. </p> @@ -50,7 +50,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">arithmetic operators</indexterm> + <indexterm audience="hidden">arithmetic operators</indexterm> The arithmetic operators use expressions with a left-hand argument, the operator, and then (in most cases) a right-hand argument. </p> @@ -195,7 +195,7 @@ where nation.item.n_nationkey < 5; <conbody> <p> - <indexterm audience="Cloudera">BETWEEN operator</indexterm> + <indexterm audience="hidden">BETWEEN operator</indexterm> In a <codeph>WHERE</codeph> clause, compares an expression to both a lower and upper bound. The comparison is successful is the expression is greater than or equal to the lower bound, and less than or equal to the upper bound. If the bound values are switched, so the lower bound is greater than the upper bound, does not match any values. @@ -287,7 +287,7 @@ where nation.item.n_nationkey between 3 and 5 <conbody> <p> - <indexterm audience="Cloudera">comparison operators</indexterm> + <indexterm audience="hidden">comparison operators</indexterm> Impala supports the familiar comparison operators for checking equality and sort order for the column data types: </p> @@ -368,14 +368,14 @@ where nation.item.n_nationkey < 5 </concept> - <concept audience="Cloudera" rev="2.1.0" id="except"> + <concept audience="hidden" rev="2.1.0" id="except"> <title>EXCEPT Operator</title> <conbody> <p> - <indexterm audience="Cloudera">EXCEPT operator</indexterm> + <indexterm audience="hidden">EXCEPT operator</indexterm> </p> </conbody> @@ -389,9 +389,9 @@ where nation.item.n_nationkey < 5 <conbody> <p> - <indexterm audience="Cloudera">EXISTS operator</indexterm> + <indexterm audience="hidden">EXISTS operator</indexterm> - <indexterm audience="Cloudera">NOT EXISTS operator</indexterm> + <indexterm audience="hidden">NOT EXISTS operator</indexterm> The <codeph>EXISTS</codeph> operator tests whether a subquery returns any results. You typically use it to find values from one table that have corresponding values in another table. </p> @@ -651,7 +651,7 @@ ERROR: AnalysisException: couldn't resolve column reference: 'x' <conbody> <p> - <indexterm audience="Cloudera">ILIKE operator</indexterm> + <indexterm audience="hidden">ILIKE operator</indexterm> A case-insensitive comparison operator for <codeph>STRING</codeph> data, with basic wildcard capability using <codeph>_</codeph> to match a single character and <codeph>%</codeph> to match multiple characters. The argument expression must match the entire string value. Typically, it is more efficient to put any <codeph>%</codeph> wildcard match at the end of the string. @@ -743,9 +743,9 @@ select 'ABCXYZ' not like 'ab_xyz'; <conbody> <p> - <indexterm audience="Cloudera">IN operator</indexterm> + <indexterm audience="hidden">IN operator</indexterm> - <indexterm audience="Cloudera">NOT IN operator</indexterm> + <indexterm audience="hidden">NOT IN operator</indexterm> The <codeph>IN</codeph> operator compares an argument value to a set of values, and returns <codeph>TRUE</codeph> if the argument matches any value in the set. The <codeph>NOT IN</codeph> operator reverses the comparison, and checks if the argument value is not part of a set of values. @@ -940,14 +940,14 @@ SELECT COUNT(DISTINCT(visitor_id)) FROM web_traffic WHERE month IN ('January','J </concept> - <concept audience="Cloudera" rev="2.1.0" id="intersect"> + <concept audience="hidden" rev="2.1.0" id="intersect"> <title>INTERSECT Operator</title> <conbody> <p> - <indexterm audience="Cloudera">INTERSECT operator</indexterm> + <indexterm audience="hidden">INTERSECT operator</indexterm> </p> </conbody> @@ -961,7 +961,7 @@ SELECT COUNT(DISTINCT(visitor_id)) FROM web_traffic WHERE month IN ('January','J <conbody> <p> - <indexterm audience="Cloudera">IREGEXP operator</indexterm> + <indexterm audience="hidden">IREGEXP operator</indexterm> Tests whether a value matches a regular expression, using case-insensitive string comparisons. Uses the POSIX regular expression syntax where <codeph>^</codeph> and <codeph>$</codeph> match the beginning and end of the string, <codeph>.</codeph> represents any single character, <codeph>*</codeph> @@ -1042,9 +1042,9 @@ SELECT COUNT(DISTINCT(visitor_id)) FROM web_traffic WHERE month IN ('January','J <conbody> <p> - <indexterm audience="Cloudera">IS DISTINCT FROM operator</indexterm> + <indexterm audience="hidden">IS DISTINCT FROM operator</indexterm> - <indexterm audience="Cloudera">IS NOT DISTINCT FROM operator</indexterm> + <indexterm audience="hidden">IS NOT DISTINCT FROM operator</indexterm> The <codeph>IS DISTINCT FROM</codeph> operator, and its converse the <codeph>IS NOT DISTINCT FROM</codeph> operator, test whether or not values are identical. <codeph>IS NOT DISTINCT FROM</codeph> is similar to the <codeph>=</codeph> operator, and <codeph>IS DISTINCT FROM</codeph> is similar to the <codeph>!=</codeph> operator, except that <codeph>NULL</codeph> values are treated as @@ -1185,9 +1185,9 @@ select <conbody> <p> - <indexterm audience="Cloudera">IS NULL operator</indexterm> + <indexterm audience="hidden">IS NULL operator</indexterm> - <indexterm audience="Cloudera">IS NOT NULL operator</indexterm> + <indexterm audience="hidden">IS NOT NULL operator</indexterm> The <codeph>IS NULL</codeph> operator, and its converse the <codeph>IS NOT NULL</codeph> operator, test whether a specified value is <codeph><xref href="impala_literals.xml#null">NULL</xref></codeph>. Because using <codeph>NULL</codeph> with any of the other comparison operators such as <codeph>=</codeph> or <codeph>!=</codeph> also returns <codeph>NULL</codeph> rather than @@ -1252,7 +1252,7 @@ select count(*) from web_traffic where weird_http_code is not null;</codeblock> <conbody> <p> - <indexterm audience="Cloudera">LIKE operator</indexterm> + <indexterm audience="hidden">LIKE operator</indexterm> A comparison operator for <codeph>STRING</codeph> data, with basic wildcard capability using the underscore (<codeph>_</codeph>) to match a single character and the percent sign (<codeph>%</codeph>) to match multiple characters. The argument expression must match the entire string value. @@ -1299,7 +1299,7 @@ select distinct c_last_name from customer where c_last_name like 'M___';</codebl <conbody> <p> - <indexterm audience="Cloudera">logical operators</indexterm> + <indexterm audience="hidden">logical operators</indexterm> Logical operators return a <codeph>BOOLEAN</codeph> value, based on a binary or unary logical operation between arguments that are also Booleans. Typically, the argument expressions use <xref href="impala_operators.xml#comparison_operators">comparison operators</xref>. @@ -1521,7 +1521,7 @@ where <conbody> <p> - <indexterm audience="Cloudera">REGEXP operator</indexterm> + <indexterm audience="hidden">REGEXP operator</indexterm> Tests whether a value matches a regular expression. Uses the POSIX regular expression syntax where <codeph>^</codeph> and <codeph>$</codeph> match the beginning and end of the string, <codeph>.</codeph> represents any single character, <codeph>*</codeph> represents a sequence of zero or more items, <codeph>+</codeph> represents a sequence of one or more items, <codeph>?</codeph> @@ -1589,7 +1589,7 @@ where <conbody> <p> - <indexterm audience="Cloudera">RLIKE operator</indexterm> + <indexterm audience="hidden">RLIKE operator</indexterm> Synonym for the <codeph>REGEXP</codeph> operator. See <xref href="impala_operators.xml#regexp"/> for details. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_optimize_partition_key_scans.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_optimize_partition_key_scans.xml b/docs/topics/impala_optimize_partition_key_scans.xml index afdd376..070f359 100644 --- a/docs/topics/impala_optimize_partition_key_scans.xml +++ b/docs/topics/impala_optimize_partition_key_scans.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p rev="2.5.0 IMPALA-2499"> - <indexterm audience="Cloudera">OPTIMIZE_PARTITION_KEY_SCANS query option</indexterm> + <indexterm audience="hidden">OPTIMIZE_PARTITION_KEY_SCANS query option</indexterm> Enables a fast code path for queries that apply simple aggregate functions to partition key columns: <codeph>MIN(<varname>key_column</varname>)</codeph>, <codeph>MAX(<varname>key_column</varname>)</codeph>, or <codeph>COUNT(DISTINCT <varname>key_column</varname>)</codeph>. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_parquet.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet.xml b/docs/topics/impala_parquet.xml index 0a34413..0a0f4f5 100644 --- a/docs/topics/impala_parquet.xml +++ b/docs/topics/impala_parquet.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Parquet support in Impala</indexterm> + <indexterm audience="hidden">Parquet support in Impala</indexterm> Impala helps you to create, manage, and query Parquet tables. Parquet is a column-oriented binary file format intended to be highly efficient for the types of large-scale queries that Impala is best at. Parquet is especially good for queries scanning particular columns within a table, for example to query <q>wide</q> @@ -443,7 +443,7 @@ Add an example here. <conbody> <p> - <indexterm audience="Cloudera">COMPRESSION_CODEC query option</indexterm> + <indexterm audience="hidden">COMPRESSION_CODEC query option</indexterm> When Impala writes Parquet data files using the <codeph>INSERT</codeph> statement, the underlying compression is controlled by the <codeph>COMPRESSION_CODEC</codeph> query option. (Prior to Impala 2.0, the query option name was <codeph>PARQUET_COMPRESSION_CODEC</codeph>.) The allowed values for this query option @@ -461,7 +461,7 @@ Add an example here. <conbody> <p> - <indexterm audience="Cloudera">compression</indexterm> + <indexterm audience="hidden">compression</indexterm> By default, the underlying data files for a Parquet table are compressed with Snappy. The combination of fast compression and decompression makes it a good choice for many data sets. To ensure Snappy compression is used, for example after experimenting with other compression codecs, set the http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_parquet_annotate_strings_utf8.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet_annotate_strings_utf8.xml b/docs/topics/impala_parquet_annotate_strings_utf8.xml index a10f117..9437fed 100644 --- a/docs/topics/impala_parquet_annotate_strings_utf8.xml +++ b/docs/topics/impala_parquet_annotate_strings_utf8.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p rev="2.6.0 IMPALA-2069"> - <indexterm audience="Cloudera">PARQUET_ANNOTATE_STRINGS_UTF8 query option</indexterm> + <indexterm audience="hidden">PARQUET_ANNOTATE_STRINGS_UTF8 query option</indexterm> Causes Impala <codeph>INSERT</codeph> and <codeph>CREATE TABLE AS SELECT</codeph> statements to write Parquet files that use the UTF-8 annotation for <codeph>STRING</codeph> columns. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_parquet_compression_codec.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet_compression_codec.xml b/docs/topics/impala_parquet_compression_codec.xml index 6f3c3cc..d1f146c 100644 --- a/docs/topics/impala_parquet_compression_codec.xml +++ b/docs/topics/impala_parquet_compression_codec.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">PARQUET_COMPRESSION_CODEC query option</indexterm> + <indexterm audience="hidden">PARQUET_COMPRESSION_CODEC query option</indexterm> Deprecated. Use <codeph>COMPRESSION_CODEC</codeph> in Impala 2.0 and later. See <xref href="impala_compression_codec.xml#compression_codec"/> for details. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_parquet_fallback_schema_resolution.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet_fallback_schema_resolution.xml b/docs/topics/impala_parquet_fallback_schema_resolution.xml index 1603e61..826839d 100644 --- a/docs/topics/impala_parquet_fallback_schema_resolution.xml +++ b/docs/topics/impala_parquet_fallback_schema_resolution.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p rev="2.6.0 IMPALA-2835 CDH-33330"> - <indexterm audience="Cloudera">PARQUET_FALLBACK_SCHEMA_RESOLUTION query option</indexterm> + <indexterm audience="hidden">PARQUET_FALLBACK_SCHEMA_RESOLUTION query option</indexterm> Allows Impala to look up columns within Parquet files by column name, rather than column order, when necessary. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_parquet_file_size.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_parquet_file_size.xml b/docs/topics/impala_parquet_file_size.xml index 42d6645..2471feb 100644 --- a/docs/topics/impala_parquet_file_size.xml +++ b/docs/topics/impala_parquet_file_size.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">PARQUET_FILE_SIZE query option</indexterm> + <indexterm audience="hidden">PARQUET_FILE_SIZE query option</indexterm> Specifies the maximum size of each Parquet data file produced by Impala <codeph>INSERT</codeph> statements. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_partitioning.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_partitioning.xml b/docs/topics/impala_partitioning.xml index 31fdcfc..4d723ad 100644 --- a/docs/topics/impala_partitioning.xml +++ b/docs/topics/impala_partitioning.xml @@ -41,7 +41,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">partitioning</indexterm> + <indexterm audience="hidden">partitioning</indexterm> By default, all the data files for a table are located in a single directory. Partitioning is a technique for physically dividing the data during loading, based on values from one or more columns, to speed up queries that test those columns. For example, with a <codeph>school_records</codeph> table partitioned on a <codeph>year</codeph> column, there is a separate data directory for each @@ -332,7 +332,7 @@ insert into weather <b>partition (year=2014, month=04, day)</b> select 'sunny',2 <conbody> <p rev="1.2.2"> - <indexterm audience="Cloudera">predicate propagation</indexterm> + <indexterm audience="hidden">predicate propagation</indexterm> Impala can even do partition pruning in cases where the partition key column is not directly compared to a constant, by applying the transitive property to other parts of the <codeph>WHERE</codeph> clause. This technique is known as predicate propagation, and is available in Impala 1.2.2 and later. In this example, the census table includes another column indicating when the data was @@ -575,7 +575,7 @@ SELECT COUNT(*) FROM sales_table WHERE year IN (2005, 2010, 2015); </concept> - <concept rev="kudu" id="partition_kudu" audience="Cloudera"> + <concept rev="kudu" id="partition_kudu" audience="hidden"> <title>Using Partitioning with Kudu Tables</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_perf_hdfs_caching.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_hdfs_caching.xml b/docs/topics/impala_perf_hdfs_caching.xml index 017c436..79d700a 100644 --- a/docs/topics/impala_perf_hdfs_caching.xml +++ b/docs/topics/impala_perf_hdfs_caching.xml @@ -469,11 +469,11 @@ Found 122 entries </li> </ul> - <p audience="Cloudera"> + <p audience="hidden"> <b>Cloudera Manager:</b> </p> - <ul audience="Cloudera"> + <ul audience="hidden"> <li> You can enable or disable HDFS caching through Cloudera Manager, using the configuration setting <uicontrol>Maximum Memory Used for Caching</uicontrol> for the HDFS service. This control sets the HDFS http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_perf_stats.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_stats.xml b/docs/topics/impala_perf_stats.xml index f0d1428..e08fd0b 100644 --- a/docs/topics/impala_perf_stats.xml +++ b/docs/topics/impala_perf_stats.xml @@ -744,7 +744,7 @@ EXPLAIN SELECT ... FROM t1 WHERE year BETWEEN 2006 AND 2009; <!-- Might deserve its own conceptual topic at some point. --> - <concept audience="Cloudera" rev="1.2.2" id="perf_stats_joins"> + <concept audience="hidden" rev="1.2.2" id="perf_stats_joins"> <title>How Statistics Are Used in Join Queries</title> @@ -756,7 +756,7 @@ EXPLAIN SELECT ... FROM t1 WHERE year BETWEEN 2006 AND 2009; <!-- Might deserve its own conceptual topic at some point. --> - <concept audience="Cloudera" rev="1.2.2" id="perf_stats_inserts"> + <concept audience="hidden" rev="1.2.2" id="perf_stats_inserts"> <title>How Statistics Are Used in INSERT Operations</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_performance.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_performance.xml b/docs/topics/impala_performance.xml index ac55bda..c0afc32 100644 --- a/docs/topics/impala_performance.xml +++ b/docs/topics/impala_performance.xml @@ -101,7 +101,7 @@ under the License. Impala can use. </li> - <li rev="1.2" audience="Cloudera"> + <li rev="1.2" audience="hidden"> <xref href="impala_perf_hdfs_caching.xml#hdfs_caching"/>. Impala can use the HDFS caching feature to pin frequently accessed data in memory, reducing disk I/O. </li> @@ -120,28 +120,28 @@ under the License. <!-- Empty/hidden stub sections that might be worth expanding later. --> - <concept id="perf_network" audience="Cloudera"> + <concept id="perf_network" audience="hidden"> <title>Network Traffic</title> <conbody/> </concept> - <concept id="perf_partition_schema" audience="Cloudera"> + <concept id="perf_partition_schema" audience="hidden"> <title>Designing Partitioned Tables</title> <conbody/> </concept> - <concept id="perf_partition_query" audience="Cloudera"> + <concept id="perf_partition_query" audience="hidden"> <title>Queries on Partitioned Tables</title> <conbody/> </concept> - <concept id="perf_monitoring" audience="Cloudera"> + <concept id="perf_monitoring" audience="hidden"> <title>Monitoring Performance through the Impala Web Interface</title> <prolog> @@ -153,42 +153,42 @@ under the License. <conbody/> </concept> - <concept id="perf_query_coord" audience="Cloudera"> + <concept id="perf_query_coord" audience="hidden"> <title>Query Coordination</title> <conbody/> </concept> - <concept id="perf_bottlenecks" audience="Cloudera"> + <concept id="perf_bottlenecks" audience="hidden"> <title>Performance Bottlenecks</title> <conbody/> </concept> - <concept id="perf_long_queries" audience="Cloudera"> + <concept id="perf_long_queries" audience="hidden"> <title>Managing Long-Running Queries</title> <conbody/> </concept> - <concept id="perf_load" audience="Cloudera"> + <concept id="perf_load" audience="hidden"> <title>Performance Considerations for Loading Data</title> <conbody/> </concept> - <concept id="perf_file_formats" audience="Cloudera"> + <concept id="perf_file_formats" audience="hidden"> <title>Performance Considerations for File Formats</title> <conbody/> </concept> - <concept id="perf_compression" audience="Cloudera"> + <concept id="perf_compression" audience="hidden"> <title>Performance Considerations for Compression</title> <prolog> @@ -200,7 +200,7 @@ under the License. <conbody/> </concept> - <concept id="perf_codegen" audience="Cloudera"> + <concept id="perf_codegen" audience="hidden"> <title>Native Code Generation</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_planning.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_planning.xml b/docs/topics/impala_planning.xml index 306d141..2b8ea0e 100644 --- a/docs/topics/impala_planning.xml +++ b/docs/topics/impala_planning.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">planning</indexterm> + <indexterm audience="hidden">planning</indexterm> Before you set up Impala in production, do some planning to make sure that your hardware setup has sufficient capacity, that your cluster topology is optimal for Impala queries, and that your schema design and ETL processes follow the best practices for Impala. http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_porting.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_porting.xml b/docs/topics/impala_porting.xml index 166691c..f9f2081 100644 --- a/docs/topics/impala_porting.xml +++ b/docs/topics/impala_porting.xml @@ -41,7 +41,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">porting</indexterm> + <indexterm audience="hidden">porting</indexterm> Although Impala uses standard SQL for queries, you might need to modify SQL source when bringing applications to Impala, due to variations in data types, built-in functions, vendor language extensions, and Hadoop-specific syntax. Even when SQL is working correctly, you might make further minor modifications for http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_ports.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_ports.xml b/docs/topics/impala_ports.xml index 3c90a3f..11f8e1e 100644 --- a/docs/topics/impala_ports.xml +++ b/docs/topics/impala_ports.xml @@ -35,7 +35,7 @@ under the License. <conbody id="conbody_ports"> <p> - <indexterm audience="Cloudera">ports</indexterm> + <indexterm audience="hidden">ports</indexterm> Impala uses the TCP ports listed in the following table. Before deploying Impala, ensure these ports are open on each system. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_prefetch_mode.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_prefetch_mode.xml b/docs/topics/impala_prefetch_mode.xml index 9c908fb..71521f8 100644 --- a/docs/topics/impala_prefetch_mode.xml +++ b/docs/topics/impala_prefetch_mode.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p rev="2.6.0 IMPALA-3286"> - <indexterm audience="Cloudera">PREFETCH_MODE query option</indexterm> + <indexterm audience="hidden">PREFETCH_MODE query option</indexterm> Determines whether the prefetching optimization is applied during join query processing. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_prereqs.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_prereqs.xml b/docs/topics/impala_prereqs.xml index f122ee7..47e54fa 100644 --- a/docs/topics/impala_prereqs.xml +++ b/docs/topics/impala_prereqs.xml @@ -43,8 +43,8 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">prerequisites</indexterm> - <indexterm audience="Cloudera">requirements</indexterm> + <indexterm audience="hidden">prerequisites</indexterm> + <indexterm audience="hidden">requirements</indexterm> To perform as expected, Impala depends on the availability of the software, hardware, and configurations described in the following sections. </p> @@ -83,14 +83,14 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">software requirements</indexterm> - <indexterm audience="Cloudera">Red Hat Enterprise Linux</indexterm> - <indexterm audience="Cloudera">RHEL</indexterm> - <indexterm audience="Cloudera">CentOS</indexterm> - <indexterm audience="Cloudera">SLES</indexterm> - <indexterm audience="Cloudera">Ubuntu</indexterm> - <indexterm audience="Cloudera">SUSE</indexterm> - <indexterm audience="Cloudera">Debian</indexterm> The relevant supported operating systems + <indexterm audience="hidden">software requirements</indexterm> + <indexterm audience="hidden">Red Hat Enterprise Linux</indexterm> + <indexterm audience="hidden">RHEL</indexterm> + <indexterm audience="hidden">CentOS</indexterm> + <indexterm audience="hidden">SLES</indexterm> + <indexterm audience="hidden">Ubuntu</indexterm> + <indexterm audience="hidden">SUSE</indexterm> + <indexterm audience="hidden">Debian</indexterm> The relevant supported operating systems and versions for Impala are the same as for the corresponding CDH 5 platforms. For details, see the <cite>Supported Operating Systems</cite> page for <ph audience="integrated"><xref href="rn_consolidated_pcm.xml#cdh_cm_supported_os">CDH @@ -113,9 +113,9 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Hive</indexterm> - <indexterm audience="Cloudera">MySQL</indexterm> - <indexterm audience="Cloudera">PostgreSQL</indexterm> + <indexterm audience="hidden">Hive</indexterm> + <indexterm audience="hidden">MySQL</indexterm> + <indexterm audience="hidden">PostgreSQL</indexterm> Impala can interoperate with data stored in Hive, and uses the same infrastructure as Hive for tracking metadata about schema objects such as tables and columns. The following components are prerequisites for Impala: @@ -193,8 +193,8 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">Java</indexterm> - <indexterm audience="Cloudera">impala-dependencies.jar</indexterm> + <indexterm audience="hidden">Java</indexterm> + <indexterm audience="hidden">impala-dependencies.jar</indexterm> Although Impala is primarily written in C++, it does use Java to communicate with various Hadoop components: </p> @@ -237,7 +237,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">network configuration</indexterm> + <indexterm audience="hidden">network configuration</indexterm> As part of ensuring best performance, Impala attempts to complete tasks on local data, as opposed to using network connections to work with remote data. To support this goal, Impala matches the <b>hostname</b> provided to each Impala daemon with the <b>IP address</b> of each DataNode by @@ -265,14 +265,14 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">hardware requirements</indexterm> - <indexterm audience="Cloudera">capacity</indexterm> - <indexterm audience="Cloudera">RAM</indexterm> - <indexterm audience="Cloudera">memory</indexterm> - <indexterm audience="Cloudera">CPU</indexterm> - <indexterm audience="Cloudera">processor</indexterm> - <indexterm audience="Cloudera">Intel</indexterm> - <indexterm audience="Cloudera">AMD</indexterm> + <indexterm audience="hidden">hardware requirements</indexterm> + <indexterm audience="hidden">capacity</indexterm> + <indexterm audience="hidden">RAM</indexterm> + <indexterm audience="hidden">memory</indexterm> + <indexterm audience="hidden">CPU</indexterm> + <indexterm audience="hidden">processor</indexterm> + <indexterm audience="hidden">Intel</indexterm> + <indexterm audience="hidden">AMD</indexterm> During join operations, portions of data from each joined table are loaded into memory. Data sets can be very large, so ensure your hardware has sufficient memory to accommodate the joins you anticipate completing. @@ -333,9 +333,9 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">impala user</indexterm> - <indexterm audience="Cloudera">impala group</indexterm> - <indexterm audience="Cloudera">root user</indexterm> + <indexterm audience="hidden">impala user</indexterm> + <indexterm audience="hidden">impala group</indexterm> + <indexterm audience="hidden">root user</indexterm> Impala creates and uses a user and group named <codeph>impala</codeph>. Do not delete this account or group and do not modify the account's or group's permissions and rights. Ensure no existing systems obstruct the functioning of these accounts and groups. For example, if you have scripts that delete user accounts not in @@ -343,7 +343,7 @@ under the License. </p> <!-- Taking out because no longer applicable in CDH 5.5 and up. --> - <p id="impala_hdfs_group" rev="1.2" audience="Cloudera"> + <p id="impala_hdfs_group" rev="1.2" audience="hidden"> For the resource management feature to work (in combination with CDH 5 and the YARN and Llama components), the <codeph>impala</codeph> user must be a member of the <codeph>hdfs</codeph> group. This setup is performed automatically during a new install, but not when upgrading from earlier Impala releases to Impala http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_processes.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_processes.xml b/docs/topics/impala_processes.xml index 6bba031..a97a644 100644 --- a/docs/topics/impala_processes.xml +++ b/docs/topics/impala_processes.xml @@ -33,9 +33,9 @@ under the License. <conbody> <p rev="1.2"> - <indexterm audience="Cloudera">state store</indexterm> - <indexterm audience="Cloudera">starting services</indexterm> - <indexterm audience="Cloudera">services</indexterm> + <indexterm audience="hidden">state store</indexterm> + <indexterm audience="hidden">starting services</indexterm> + <indexterm audience="hidden">services</indexterm> To activate Impala if it is installed but not yet started: </p> @@ -69,7 +69,7 @@ under the License. <p outputclass="toc inpage"/> </conbody> - <concept id="starting_via_cm" audience="Cloudera"> + <concept id="starting_via_cm" audience="hidden"> <title>Starting Impala through Cloudera Manager</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_proxy.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_proxy.xml b/docs/topics/impala_proxy.xml index f064961..bf46a37 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"> + <li audience="hidden"> On systems managed by Cloudera Manager, on the page <menucascade><uicontrol>Impala</uicontrol><uicontrol>Configuration</uicontrol><uicontrol>Impala Daemon Default Group</uicontrol></menucascade>, specify a value for the <uicontrol>Impala Daemons Load @@ -170,7 +170,7 @@ under the License. </concept> - <concept id="proxy_balancing" rev="CDH-33836 DOCS-349 CDH-39925 CDH-36812" audience="Cloudera"> + <concept id="proxy_balancing" rev="CDH-33836 DOCS-349 CDH-39925 CDH-36812" audience="hidden"> <title>Choosing the Load-Balancing Algorithm</title> <conbody> <p> @@ -269,7 +269,7 @@ under the License. running the <cmdname>impalad</cmdname> daemon. </li> - <li rev="CDH-40363" audience="Cloudera"> + <li rev="CDH-40363" audience="hidden"> 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> --be_principal=impala/<varname>actual_host</varname>@<varname>realm</varname> --keytab_file=<varname>path_to_merged_keytab</varname></codeblock> - <note audience="Cloudera"> + <note audience="hidden"> <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. </note> </li> - <li audience="Cloudera"> + <li audience="hidden"> 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. </li> @@ -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: <ul> - <li audience="Cloudera"> + <li audience="hidden"> On a cluster managed by Cloudera Manager, restart the Impala service. </li> @@ -522,11 +522,11 @@ listen impalajdbc :21051 <note conref="../shared/impala_common.xml#common/proxy_jdbc_caveat"/> - <p audience="Cloudera"> + <p audience="hidden"> The following example shows extra steps needed for a cluster using Kerberos authentication: </p> -<codeblock audience="Cloudera">$ klist +<codeblock audience="hidden">$ klist $ impala-shell -k $ kinit -r 1d -kt /systest/keytabs/hdfs.keytab hdfs $ impala-shell -i c2104.hal.cloudera.com:21000 http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_query_timeout_s.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_query_timeout_s.xml b/docs/topics/impala_query_timeout_s.xml index 3fb40cd..e41c087 100644 --- a/docs/topics/impala_query_timeout_s.xml +++ b/docs/topics/impala_query_timeout_s.xml @@ -35,7 +35,7 @@ under the License. <conbody> <p rev="2.0.0"> - <indexterm audience="Cloudera">QUERY_TIMEOUT_S query option</indexterm> + <indexterm audience="hidden">QUERY_TIMEOUT_S query option</indexterm> Sets the idle query timeout value for the session, in seconds. Queries that sit idle for longer than the timeout value are automatically cancelled. If the system administrator specified the <codeph>--idle_query_timeout</codeph> startup option, <codeph>QUERY_TIMEOUT_S</codeph> must be smaller than http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_rcfile.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_rcfile.xml b/docs/topics/impala_rcfile.xml index 31d5a0c..ed5b029 100644 --- a/docs/topics/impala_rcfile.xml +++ b/docs/topics/impala_rcfile.xml @@ -36,7 +36,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">RCFile support in Impala</indexterm> + <indexterm audience="hidden">RCFile support in Impala</indexterm> Impala supports using RCFile data files. </p> @@ -167,7 +167,7 @@ Returned 3 row(s) in 0.23s</codeblock> <conbody> <p> - <indexterm audience="Cloudera">compression</indexterm> + <indexterm audience="hidden">compression</indexterm> You may want to enable compression on existing tables. Enabling compression provides performance gains in most cases and is supported for RCFile tables. For example, to enable Snappy compression, you would specify the following additional settings when loading data through the Hive shell: @@ -250,7 +250,7 @@ hive> INSERT OVERWRITE TABLE tbl_rc PARTITION(year) SELECT * FROM tbl;</codeb </conbody> </concept> - <concept audience="Cloudera" id="rcfile_data_types"> + <concept audience="hidden" id="rcfile_data_types"> <title>Data Type Considerations for RCFile Tables</title> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_refresh.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_refresh.xml b/docs/topics/impala_refresh.xml index d0e3d22..8244aa4 100644 --- a/docs/topics/impala_refresh.xml +++ b/docs/topics/impala_refresh.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">REFRESH statement</indexterm> + <indexterm audience="hidden">REFRESH statement</indexterm> To accurately respond to queries, the Impala node that acts as the coordinator (the node to which you are connected through <cmdname>impala-shell</cmdname>, JDBC, or ODBC) must have current metadata about those databases and tables that are referenced in Impala queries. If you are not familiar with the way Impala uses http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_replica_preference.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_replica_preference.xml b/docs/topics/impala_replica_preference.xml index 3398403..610bd35 100644 --- a/docs/topics/impala_replica_preference.xml +++ b/docs/topics/impala_replica_preference.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p rev="2.7.0"> - <indexterm audience="Cloudera">REPLICA_PREFERENCE query option</indexterm> + <indexterm audience="hidden">REPLICA_PREFERENCE query option</indexterm> </p> <p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_request_pool.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_request_pool.xml b/docs/topics/impala_request_pool.xml index d9a6210..625dc87 100644 --- a/docs/topics/impala_request_pool.xml +++ b/docs/topics/impala_request_pool.xml @@ -37,7 +37,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">REQUEST_POOL query option</indexterm> + <indexterm audience="hidden">REQUEST_POOL query option</indexterm> The pool or queue name that queries should be submitted to. Only applies when you enable the Impala admission control feature. Specifies the name of the pool used by requests from Impala to the resource manager. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_reservation_request_timeout.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_reservation_request_timeout.xml b/docs/topics/impala_reservation_request_timeout.xml index c350728..6f70cfd 100644 --- a/docs/topics/impala_reservation_request_timeout.xml +++ b/docs/topics/impala_reservation_request_timeout.xml @@ -39,7 +39,7 @@ under the License. <note conref="../shared/impala_common.xml#common/llama_query_options_obsolete"/> <p> - <indexterm audience="Cloudera">RESERVATION_REQUEST_TIMEOUT query option</indexterm> + <indexterm audience="hidden">RESERVATION_REQUEST_TIMEOUT query option</indexterm> Maximum number of milliseconds Impala will wait for a reservation to be completely granted or denied. Used in conjunction with the Impala resource management feature in Impala 1.2 and higher with CDH 5. </p> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_reserved_words.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_reserved_words.xml b/docs/topics/impala_reserved_words.xml index 080735a..423fd43 100644 --- a/docs/topics/impala_reserved_words.xml +++ b/docs/topics/impala_reserved_words.xml @@ -34,7 +34,7 @@ under the License. <conbody> <p> - <indexterm audience="Cloudera">reserved words</indexterm> + <indexterm audience="hidden">reserved words</indexterm> The following are the reserved words for the current release of Impala. A reserved word is one that cannot be used directly as an identifier; you must quote it with backticks. For example, a statement <codeph>CREATE TABLE select (x INT)</codeph> fails, while <codeph>CREATE TABLE `select` (x INT)</codeph> http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_resource_management.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_resource_management.xml b/docs/topics/impala_resource_management.xml index c16f367..bc98014 100644 --- a/docs/topics/impala_resource_management.xml +++ b/docs/topics/impala_resource_management.xml @@ -44,7 +44,7 @@ under the License. <p outputclass="toc inpage"/> </conbody> - <concept audience="Cloudera" id="llama"> + <concept audience="hidden" id="llama"> <!-- Hiding the whole concept now that Llama is desupported. --> <title>The Llama Daemon</title> @@ -315,14 +315,14 @@ under the License. <conbody> -<!-- Conditionalizing some content here with audience="Cloudera" because there are already some XML comments +<!-- Conditionalizing some content here with audience="hidden" because there are already some XML comments inside the list, so not practical to enclose the whole thing in XML comments. --> - <p audience="Cloudera"> + <p audience="hidden"> Currently, Impala in CDH 5 has the following limitations for resource management of Impala queries: </p> - <ul audience="Cloudera"> + <ul audience="hidden"> <li> Table statistics are required, and column statistics are highly valuable, for Impala to produce accurate estimates of how much memory to request from YARN. See http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_revoke.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_revoke.xml b/docs/topics/impala_revoke.xml index 28137ea..97a912d 100644 --- a/docs/topics/impala_revoke.xml +++ b/docs/topics/impala_revoke.xml @@ -40,7 +40,7 @@ under the License. <conbody> <p rev="2.0.0"> - <indexterm audience="Cloudera">REVOKE statement</indexterm> + <indexterm audience="hidden">REVOKE statement</indexterm> <!-- Copied from Sentry docs. Turn into conref. I did some rewording for clarity. --> The <codeph>REVOKE</codeph> statement revokes roles or privileges on a specified object from groups. Only Sentry administrative users can revoke the role from a group. The revocation has a cascading effect. For http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/8377b994/docs/topics/impala_rm_initial_mem.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_rm_initial_mem.xml b/docs/topics/impala_rm_initial_mem.xml index e63f70a..fd9f819 100644 --- a/docs/topics/impala_rm_initial_mem.xml +++ b/docs/topics/impala_rm_initial_mem.xml @@ -33,7 +33,7 @@ under the License. <conbody> <p rev="2.5.0"> - <indexterm audience="Cloudera">RM_INITIAL_MEM query option</indexterm> + <indexterm audience="hidden">RM_INITIAL_MEM query option</indexterm> </p> <p>
