You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jr...@apache.org on 2017/03/10 23:57:12 UTC
incubator-impala git commit: MPALA-3402: [DOCS] Remove CDH- JIRA
numbers from rev=
Repository: incubator-impala
Updated Branches:
refs/heads/master def5355a2 -> f3820e620
MPALA-3402: [DOCS] Remove CDH- JIRA numbers from rev=
For history and tracking purposes, there are many
instances of rev="CDH-1234" for various CDH- JIRA
numbers. This produces no visible output, it's just
FYI for the person editing the source. Removing all
these now from the upstream doc source, so as not
to have "CDH" all through the doc source files.
Change-Id: I29089e5a31cd72e876b2ccb8375d1c10693c6aba
Reviewed-on: http://gerrit.cloudera.org:8080/6349
Reviewed-by: Ambreen Kazi <am...@cloudera.com>
Reviewed-by: John Russell <jr...@cloudera.com>
Tested-by: Impala Public Jenkins
Project: http://git-wip-us.apache.org/repos/asf/incubator-impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-impala/commit/f3820e62
Tree: http://git-wip-us.apache.org/repos/asf/incubator-impala/tree/f3820e62
Diff: http://git-wip-us.apache.org/repos/asf/incubator-impala/diff/f3820e62
Branch: refs/heads/master
Commit: f3820e62055135da32746d156b3e00f1ff5b59a6
Parents: def5355
Author: John Russell <jr...@cloudera.com>
Authored: Fri Mar 10 13:39:20 2017 -0800
Committer: Impala Public Jenkins <im...@gerrit.cloudera.org>
Committed: Fri Mar 10 23:56:51 2017 +0000
----------------------------------------------------------------------
docs/topics/impala_admission.xml | 2 +-
docs/topics/impala_alter_table.xml | 48 ++++++++++----------
docs/topics/impala_avro.xml | 2 +-
docs/topics/impala_breakpad.xml | 6 +--
docs/topics/impala_create_database.xml | 4 +-
docs/topics/impala_create_table.xml | 8 ++--
docs/topics/impala_datetime_functions.xml | 2 +-
docs/topics/impala_drop_database.xml | 2 +-
docs/topics/impala_drop_stats.xml | 2 +-
docs/topics/impala_drop_table.xml | 4 +-
docs/topics/impala_explain.xml | 2 +-
docs/topics/impala_explain_plan.xml | 2 +-
docs/topics/impala_insert.xml | 2 +-
docs/topics/impala_invalidate_metadata.xml | 2 +-
docs/topics/impala_kerberos.xml | 2 +-
docs/topics/impala_langref_unsupported.xml | 2 +-
docs/topics/impala_max_scan_range_length.xml | 2 +-
docs/topics/impala_mem_limit.xml | 26 +++++------
docs/topics/impala_operators.xml | 2 +-
docs/topics/impala_parquet.xml | 2 +-
...mpala_parquet_fallback_schema_resolution.xml | 4 +-
docs/topics/impala_partitioning.xml | 2 +-
docs/topics/impala_proxy.xml | 4 +-
docs/topics/impala_refresh.xml | 22 ++++-----
.../topics/impala_runtime_bloom_filter_size.xml | 4 +-
docs/topics/impala_runtime_filter_max_size.xml | 2 +-
docs/topics/impala_runtime_filter_min_size.xml | 2 +-
docs/topics/impala_runtime_filter_mode.xml | 6 +--
docs/topics/impala_s3_skip_insert_staging.xml | 4 +-
docs/topics/impala_scalability.xml | 2 +-
docs/topics/impala_schedule_random_replica.xml | 2 +-
docs/topics/impala_select.xml | 2 +-
docs/topics/impala_shell_commands.xml | 2 +-
docs/topics/impala_shell_running_commands.xml | 8 ++--
docs/topics/impala_string_functions.xml | 2 +-
docs/topics/impala_troubleshooting.xml | 2 +-
docs/topics/impala_truncate_table.xml | 2 +-
37 files changed, 98 insertions(+), 98 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_admission.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_admission.xml b/docs/topics/impala_admission.xml
index dbee3e2..0878d6e 100644
--- a/docs/topics/impala_admission.xml
+++ b/docs/topics/impala_admission.xml
@@ -301,7 +301,7 @@ under the License.
</ul>
- <p rev="CDH-27667">
+ <p rev="">
In Impala 2.0 and higher, you can submit
a SQL <codeph>SET</codeph> statement from the client application
to change the <codeph>REQUEST_POOL</codeph> query option.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_alter_table.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_alter_table.xml b/docs/topics/impala_alter_table.xml
index a3f1e19..5c94303 100644
--- a/docs/topics/impala_alter_table.xml
+++ b/docs/topics/impala_alter_table.xml
@@ -70,7 +70,7 @@ ALTER TABLE <varname>name</varname> DROP [IF EXISTS] PARTITION (<varname>partiti
<ph rev="2.3.0">[PURGE]</ph>
<ph rev="kudu">ALTER TABLE <varname>name</varname> DROP [IF EXISTS] RANGE PARTITION <varname>kudu_partition_spec</varname></ph>
-<ph rev="2.3.0 IMPALA-1568 CDH-36799">ALTER TABLE <varname>name</varname> RECOVER PARTITIONS</ph>
+<ph rev="2.3.0 IMPALA-1568">ALTER TABLE <varname>name</varname> RECOVER PARTITIONS</ph>
ALTER TABLE <varname>name</varname> [PARTITION (<varname>partition_spec</varname>)]
SET { FILEFORMAT <varname>file_format</varname>
@@ -219,7 +219,7 @@ alter table fast_growing_data partition (year = 2016, month in (10,11,12)) set f
<p conref="../shared/impala_common.xml#common/s3_blurb"/>
- <p rev="2.6.0 CDH-39913 IMPALA-1878">
+ <p rev="2.6.0 IMPALA-1878">
You can specify an <codeph>s3a://</codeph> prefix on the <codeph>LOCATION</codeph> attribute of a table or partition
to make Impala query data from the Amazon S3 filesystem. In <keyword keyref="impala26_full"/> and higher, Impala automatically
handles creating or removing the associated folders when you issue <codeph>ALTER TABLE</codeph> statements
@@ -315,11 +315,11 @@ alter table p1 partition (month=1, day=1) set location '/usr/external_data/new_y
<note conref="../shared/impala_common.xml#common/add_partition_set_location"/>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
<b>To automatically detect new partition directories added through Hive or HDFS operations:</b>
</p>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
In <keyword keyref="impala23_full"/> and higher, the <codeph>RECOVER PARTITIONS</codeph> clause scans
a partitioned table to detect if any new partition directories were added outside of Impala,
such as by Hive <codeph>ALTER TABLE</codeph> statements or by <cmdname>hdfs dfs</cmdname>
@@ -328,17 +328,17 @@ alter table p1 partition (month=1, day=1) set location '/usr/external_data/new_y
the <codeph>REFRESH</codeph> statement does.
</p>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
For example, here is a sequence of examples showing how you might create a partitioned table in Impala,
create new partitions through Hive, copy data files into the new partitions with the <cmdname>hdfs</cmdname>
command, and have Impala recognize the new partitions and new data:
</p>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
In Impala, create the table, and a single partition for demonstration purposes:
</p>
-<codeblock rev="2.3.0 IMPALA-1568 CDH-36799">
+<codeblock rev="2.3.0 IMPALA-1568">
<![CDATA[
create database recover_partitions;
use recover_partitions;
@@ -354,12 +354,12 @@ quit;
]]>
</codeblock>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
In Hive, create some new partitions. In a real use case, you might create the
partitions and populate them with data as the final stages of an ETL pipeline.
</p>
-<codeblock rev="2.3.0 IMPALA-1568 CDH-36799">
+<codeblock rev="2.3.0 IMPALA-1568">
<![CDATA[
hive> use recover_partitions;
OK
@@ -371,12 +371,12 @@ hive> quit;
]]>
</codeblock>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
For demonstration purposes, manually copy data (a single row) into these
new partitions, using manual HDFS operations:
</p>
-<codeblock rev="2.3.0 IMPALA-1568 CDH-36799">
+<codeblock rev="2.3.0 IMPALA-1568">
<![CDATA[
$ hdfs dfs -ls /user/hive/warehouse/recover_partitions.db/t1/yy=2016/
Found 3 items
@@ -391,7 +391,7 @@ $ hdfs dfs -cp /user/hive/warehouse/recover_partitions.db/t1/yy=2016/mm=1/data.t
]]>
</codeblock>
-<codeblock rev="2.3.0 IMPALA-1568 CDH-36799">
+<codeblock rev="2.3.0 IMPALA-1568">
<![CDATA[
hive> select * from t1;
OK
@@ -402,14 +402,14 @@ hive> quit;
]]>
</codeblock>
- <p rev="2.3.0 IMPALA-1568 CDH-36799">
+ <p rev="2.3.0 IMPALA-1568">
In Impala, initially the partitions and data are not visible.
Running <codeph>ALTER TABLE</codeph> with the <codeph>RECOVER PARTITIONS</codeph>
clause scans the table data directory to find any new partition directories, and
the data files inside them:
</p>
-<codeblock rev="2.3.0 IMPALA-1568 CDH-36799">
+<codeblock rev="2.3.0 IMPALA-1568">
<![CDATA[
select * from t1;
+------------------+------+----+
@@ -514,7 +514,7 @@ ALTER TABLE <varname>table_name</varname> DROP <varname>column_name</varname>;</
to replace all the data before issuing any further queries.)
</p>
- <p rev="CDH-37178">
+ <p rev="">
For example, here is how you might add columns to an existing table.
The first <codeph>ALTER TABLE</codeph> adds two new columns, and the second
<codeph>ALTER TABLE</codeph> adds one new column.
@@ -523,7 +523,7 @@ ALTER TABLE <varname>table_name</varname> DROP <varname>column_name</varname>;</
considered to be <codeph>NULL</codeph>.
</p>
-<codeblock rev="CDH-37178">
+<codeblock rev="">
create table t1 (x int);
insert into t1 values (1), (2);
@@ -552,7 +552,7 @@ select * from t1 order by x;
define the new set of columns with a single <codeph>ALTER TABLE ... REPLACE COLUMNS</codeph> statement.
</p>
- <p rev="CDH-37178">
+ <p rev="">
The following examples show some safe operations to drop or change columns. Dropping the final column
in a table lets Impala ignore the data causing any disruption to existing data files. Changing the type
of a column works if existing data values can be safely converted to the new type. The type conversion
@@ -561,7 +561,7 @@ select * from t1 order by x;
Parquet, the rules are stricter and type conversions only work between certain sizes of integers.
</p>
-<codeblock rev="CDH-37178">
+<codeblock rev="">
create table optional_columns (x int, y int, z int, a1 int, a2 int);
insert into optional_columns values (1,2,3,0,0), (2,3,4,100,100);
@@ -580,7 +580,7 @@ select * from optional_columns;
+---+---+---+
</codeblock>
-<codeblock rev="CDH-37178">
+<codeblock rev="">
create table int_to_string (s string, x int);
insert into int_to_string values ('one', 1), ('two', 2);
@@ -602,7 +602,7 @@ select s, upper(x) from int_to_string;
+-------+----------+
</codeblock>
- <p rev="CDH-37178">
+ <p rev="">
Remember that Impala does not actually do any conversion for the underlying data files as a result of
<codeph>ALTER TABLE</codeph> statements. If you use <codeph>ALTER TABLE</codeph> to create a table
layout that does not agree with the contents of the underlying files, you must replace the files
@@ -610,7 +610,7 @@ select s, upper(x) from int_to_string;
<codeph>INSERT OVERWRITE</codeph> to copy from another table and replace the original data.
</p>
- <p rev="CDH-37178">
+ <p rev="">
The following example shows what happens if you delete the middle column from a Parquet table containing three columns.
The underlying data files still contain three columns of data. Because the columns are interpreted based on their positions in
the data file instead of the specific column names, a <codeph>SELECT *</codeph> query now reads the first and second
@@ -620,7 +620,7 @@ select s, upper(x) from int_to_string;
if you drop or change the type of a column in a way that causes problems with existing data files.
</p>
-<codeblock rev="CDH-37178">
+<codeblock rev="">
-- Parquet table showing how dropping a column can produce unexpected results.
create table p1 (s1 string, s2 string, s3 string) stored as parquet;
@@ -650,7 +650,7 @@ select * from p1;
+-------+-------+
</codeblock>
-<codeblock rev="CDH-37178">
+<codeblock rev="">
-- Parquet table showing how dropping a column can produce conversion errors.
create table p2 (s1 string, x int, s3 string) stored as parquet;
@@ -877,7 +877,7 @@ alter table sales_data add partition (zipcode = cast(9021 * 10 as string));</cod
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
Most <codeph>ALTER TABLE</codeph> clauses do not actually
read or write any HDFS files, and so do not depend on
specific HDFS permissions. For example, the <codeph>SET FILEFORMAT</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_avro.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_avro.xml b/docs/topics/impala_avro.xml
index 3ec7b99..8e07d47 100644
--- a/docs/topics/impala_avro.xml
+++ b/docs/topics/impala_avro.xml
@@ -245,7 +245,7 @@ for this information.
If there is a mismatch in column name or type, Impala uses the column definition from the Avro schema.
Because a <codeph>CHAR</codeph> or <codeph>VARCHAR</codeph> column in Impala maps to an Avro <codeph>STRING</codeph>,
this case is not considered a mismatch and the column is preserved as <codeph>CHAR</codeph> or <codeph>VARCHAR</codeph>
- in the reconciled schema. <ph rev="2.7.0 IMPALA-3687 CDH-43731">Prior to <keyword keyref="impala27_full"/> the column
+ in the reconciled schema. <ph rev="2.7.0 IMPALA-3687">Prior to <keyword keyref="impala27_full"/> the column
name and comment for such <codeph>CHAR</codeph> and <codeph>VARCHAR</codeph> columns was also taken from the SQL column definition.
In <keyword keyref="impala27_full"/> and higher, the column name and comment from the Avro schema file take precedence for such columns,
and only the <codeph>CHAR</codeph> or <codeph>VARCHAR</codeph> type is preserved from the SQL column definition.</ph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_breakpad.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_breakpad.xml b/docs/topics/impala_breakpad.xml
index 056290a..e7e2bb5 100644
--- a/docs/topics/impala_breakpad.xml
+++ b/docs/topics/impala_breakpad.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="breakpad" rev="2.6.0 IMPALA-2686 CDH-40238">
+<concept id="breakpad" rev="2.6.0 IMPALA-2686">
<title>Breakpad Minidumps for Impala (<keyword keyref="impala26"/> or higher only)</title>
<titlealts audience="PDF"><navtitle>Breakpad Minidumps</navtitle></titlealts>
@@ -33,7 +33,7 @@ under the License.
<conbody>
- <p rev="2.6.0 IMPALA-2686 CDH-40238">
+ <p rev="2.6.0 IMPALA-2686">
The <xref href="https://chromium.googlesource.com/breakpad/breakpad/" scope="external" format="html">breakpad</xref>
project is an open-source framework for crash reporting.
In <keyword keyref="impala26_full"/> and higher, Impala can use <codeph>breakpad</codeph> to record stack information and
@@ -67,7 +67,7 @@ under the License.
to the empty string, and restart the corresponding services or daemons.
</p>
- <p rev="IMPALA-3677 CDH-43745">
+ <p rev="IMPALA-3677">
In <keyword keyref="impala27_full"/> and higher,
you can send a <codeph>SIGUSR1</codeph> signal to any Impala-related daemon to write a
Breakpad minidump. For advanced troubleshooting, you can now produce a minidump
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_create_database.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_create_database.xml b/docs/topics/impala_create_database.xml
index 871bbc6..f24ff7b 100644
--- a/docs/topics/impala_create_database.xml
+++ b/docs/topics/impala_create_database.xml
@@ -120,7 +120,7 @@ under the License.
<p conref="../shared/impala_common.xml#common/s3_blurb"/>
- <p rev="2.6.0 CDH-39913 IMPALA-1878">
+ <p rev="2.6.0 IMPALA-1878">
To specify that any tables created within a database reside on the Amazon S3 system,
you can include an <codeph>s3a://</codeph> prefix on the <codeph>LOCATION</codeph>
attribute. In <keyword keyref="impala26_full"/> and higher, Impala automatically creates any
@@ -133,7 +133,7 @@ under the License.
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have write
permission for the parent HDFS directory under which the database
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_create_table.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_create_table.xml b/docs/topics/impala_create_table.xml
index 77c6452..a3c9ce8 100644
--- a/docs/topics/impala_create_table.xml
+++ b/docs/topics/impala_create_table.xml
@@ -109,7 +109,7 @@ under the License.
[COMMENT '<varname>table_comment</varname>']
[WITH SERDEPROPERTIES ('<varname>key1</varname>'='<varname>value1</varname>', '<varname>key2</varname>'='<varname>value2</varname>', ...)]
[
- [ROW FORMAT <varname>row_format</varname>] <ph rev="CDH-41501">[STORED AS <varname>ctas_file_format</varname>]</ph>
+ [ROW FORMAT <varname>row_format</varname>] <ph rev="">[STORED AS <varname>ctas_file_format</varname>]</ph>
]
[LOCATION '<varname>hdfs_path</varname>']
[TBLPROPERTIES ('<varname>key1</varname>'='<varname>value1</varname>', '<varname>key2</varname>'='<varname>value2</varname>', ...)]
@@ -153,7 +153,7 @@ file_format:
| SEQUENCEFILE
| RCFILE
-<ph rev="CDH-41501">ctas_file_format:
+<ph rev="">ctas_file_format:
PARQUET
| TEXTFILE</ph>
</codeblock>
@@ -1159,7 +1159,7 @@ ERROR: AnalysisException: Partition column name mismatch: year != month
the data files in S3.
</p>
- <p rev="2.6.0 CDH-39913 IMPALA-1878">
+ <p rev="2.6.0 IMPALA-1878">
In <keyword keyref="impala26_full"/> and higher, you can use this special
<codeph>LOCATION</codeph> syntax as part of a <codeph>CREATE TABLE AS SELECT</codeph>
statement.
@@ -1190,7 +1190,7 @@ ERROR: AnalysisException: Partition column name mismatch: year != month
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under, typically the
<codeph>impala</codeph> user, must have both execute and write permission for the database
directory where the table is being created.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_datetime_functions.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_datetime_functions.xml b/docs/topics/impala_datetime_functions.xml
index 4276c88..6d849b1 100644
--- a/docs/topics/impala_datetime_functions.xml
+++ b/docs/topics/impala_datetime_functions.xml
@@ -1135,7 +1135,7 @@ select now() as right_now,
</dlentry>
- <dlentry rev="IMPALA-1772 CDH-38381 2.6.0" id="millisecond">
+ <dlentry rev="IMPALA-1772 2.6.0" id="millisecond">
<dt>
<codeph>millisecond(timestamp)</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_drop_database.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_drop_database.xml b/docs/topics/impala_drop_database.xml
index 5dd1536..c16cd40 100644
--- a/docs/topics/impala_drop_database.xml
+++ b/docs/topics/impala_drop_database.xml
@@ -128,7 +128,7 @@ under the License.
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have write
permission for the directory associated with the database.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_drop_stats.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_drop_stats.xml b/docs/topics/impala_drop_stats.xml
index fe5a13e..b71bfed 100644
--- a/docs/topics/impala_drop_stats.xml
+++ b/docs/topics/impala_drop_stats.xml
@@ -104,7 +104,7 @@ DROP INCREMENTAL STATS [<varname>database_name</varname>.]<varname>table_name</v
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, does not need any
particular HDFS permissions to perform this statement.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_drop_table.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_drop_table.xml b/docs/topics/impala_drop_table.xml
index 318393c..86af10a 100644
--- a/docs/topics/impala_drop_table.xml
+++ b/docs/topics/impala_drop_table.xml
@@ -128,7 +128,7 @@ drop table temporary.trivial;</codeblock>
<p conref="../shared/impala_common.xml#common/disk_space_blurb"/>
<p conref="../shared/impala_common.xml#common/s3_blurb"/>
- <p rev="2.6.0 CDH-39913 IMPALA-1878">
+ <p rev="2.6.0 IMPALA-1878">
The <codeph>DROP TABLE</codeph> statement can remove data files from S3
if the associated S3 table is an internal table.
In <keyword keyref="impala26_full"/> and higher, as part of improved support for writing
@@ -144,7 +144,7 @@ drop table temporary.trivial;</codeblock>
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
For an internal table, the user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have write
permission for all the files and directories that make up the table.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_explain.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_explain.xml b/docs/topics/impala_explain.xml
index 7c4d444..fefe574 100644
--- a/docs/topics/impala_explain.xml
+++ b/docs/topics/impala_explain.xml
@@ -224,7 +224,7 @@ EXPLAIN_LEVEL set to extended
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
<!-- Doublecheck these details. Does EXPLAIN really need any permissions? -->
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have read
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_explain_plan.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_explain_plan.xml b/docs/topics/impala_explain_plan.xml
index df1eb2b..8099eb9 100644
--- a/docs/topics/impala_explain_plan.xml
+++ b/docs/topics/impala_explain_plan.xml
@@ -203,7 +203,7 @@ under the License.
reads are in effect.
</p>
- <p rev="CDH-29157">
+ <p rev="">
By default, time values in the profile output reflect the wall-clock time taken by an operation.
For values denoting system time or user time, the measurement unit is reflected in the metric
name, such as <codeph>ScannerThreadsSysTime</codeph> or <codeph>ScannerThreadsUserTime</codeph>.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_insert.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_insert.xml b/docs/topics/impala_insert.xml
index 7e7b76b..1b7dab0 100644
--- a/docs/topics/impala_insert.xml
+++ b/docs/topics/impala_insert.xml
@@ -702,7 +702,7 @@ Inserted 2 rows in 0.16s
<p conref="../shared/impala_common.xml#common/cancel_blurb_yes"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have read
permission for the files in the source directory of an <codeph>INSERT ... SELECT</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_invalidate_metadata.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_invalidate_metadata.xml b/docs/topics/impala_invalidate_metadata.xml
index b316b0d..4f63d34 100644
--- a/docs/topics/impala_invalidate_metadata.xml
+++ b/docs/topics/impala_invalidate_metadata.xml
@@ -173,7 +173,7 @@ under the License.
</p>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have execute
permissions for all the relevant directories holding table data.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_kerberos.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_kerberos.xml b/docs/topics/impala_kerberos.xml
index 643e3de..d74c8bb 100644
--- a/docs/topics/impala_kerberos.xml
+++ b/docs/topics/impala_kerberos.xml
@@ -347,7 +347,7 @@ $ chown impala:impala impala-http.keytab</codeblock>
</concept>
- <concept id="auth_to_local" rev="IMPALA-2660 CDH-40241">
+ <concept id="auth_to_local" rev="IMPALA-2660">
<title>Mapping Kerberos Principals to Short Names for Impala</title>
<conbody>
<p conref="../shared/impala_common.xml#common/auth_to_local_instructions"/>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_langref_unsupported.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_langref_unsupported.xml b/docs/topics/impala_langref_unsupported.xml
index f0c326a..dd9eff5 100644
--- a/docs/topics/impala_langref_unsupported.xml
+++ b/docs/topics/impala_langref_unsupported.xml
@@ -79,7 +79,7 @@ under the License.
Extensibility mechanisms such as <codeph>TRANSFORM</codeph>, custom file formats, or custom SerDes.
</li>
- <li rev="CDH-41376">
+ <li rev="">
The <codeph>DATE</codeph> data type.
</li>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/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 3fbd4ca..cc5978b 100644
--- a/docs/topics/impala_max_scan_range_length.xml
+++ b/docs/topics/impala_max_scan_range_length.xml
@@ -60,7 +60,7 @@ under the License.
<b>Type:</b> numeric
</p>
- <p rev="IMPALA-3799 CDH-43746">
+ <p rev="IMPALA-3799">
In <keyword keyref="impala27_full"/> and higher, the argument value can include unit specifiers,
such as <codeph>100m</codeph> or <codeph>100mb</codeph>. In previous versions,
Impala interpreted such formatted values as 0, leading to query failures.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_mem_limit.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_mem_limit.xml b/docs/topics/impala_mem_limit.xml
index 98bc470..b784989 100644
--- a/docs/topics/impala_mem_limit.xml
+++ b/docs/topics/impala_mem_limit.xml
@@ -42,7 +42,7 @@ under the License.
Therefore, the total memory that can be used by a query is the <codeph>MEM_LIMIT</codeph> times the number of nodes.
</p>
- <p rev="CDH-32135">
+ <p rev="">
There are two levels of memory limit for Impala.
The <codeph>-mem_limit</codeph> startup option sets an overall limit for the <cmdname>impalad</cmdname> process
(which handles multiple queries concurrently).
@@ -53,7 +53,7 @@ under the License.
and must always be less than the <cmdname>impalad</cmdname> memory limit.
</p>
- <p rev="CDH-32135">
+ <p rev="">
If query processing exceeds the specified memory limit on any node, either the per-query limit or the
<cmdname>impalad</cmdname> limit, Impala cancels the query automatically.
Memory limits are checked periodically during query processing, so the actual memory in use
@@ -79,26 +79,26 @@ under the License.
<b>Type:</b> numeric
</p>
- <p rev="CDH-32135">
+ <p rev="">
<b>Units:</b> A numeric argument represents memory size in bytes; you can also use a suffix of <codeph>m</codeph> or <codeph>mb</codeph>
for megabytes, or more commonly <codeph>g</codeph> or <codeph>gb</codeph> for gigabytes. If you specify a value with unrecognized
formats, subsequent queries fail with an error.
</p>
- <p rev="CDH-32135">
+ <p rev="">
<b>Default:</b> 0 (unlimited)
</p>
<p conref="../shared/impala_common.xml#common/usage_notes_blurb"/>
- <p rev="CDH-32135">
+ <p rev="">
The <codeph>MEM_LIMIT</codeph> setting is primarily useful in a high-concurrency setting,
or on a cluster with a workload shared between Impala and other data processing components.
You can prevent any query from accidentally using much more memory than expected,
which could negatively impact other Impala queries.
</p>
- <p rev="CDH-32135">
+ <p rev="">
Use the output of the <codeph>SUMMARY</codeph> command in <cmdname>impala-shell</cmdname>
to get a report of memory used for each phase of your most heavyweight queries on each node,
and then set a <codeph>MEM_LIMIT</codeph> somewhat higher than that.
@@ -106,14 +106,14 @@ under the License.
the <codeph>SUMMARY</codeph> command.
</p>
- <p conref="../shared/impala_common.xml#common/example_blurb" rev="CDH-32135"/>
+ <p conref="../shared/impala_common.xml#common/example_blurb" rev=""/>
- <p rev="CDH-32135">
+ <p rev="">
The following examples show how to set the <codeph>MEM_LIMIT</codeph> query option
using a fixed number of bytes, or suffixes representing gigabytes or megabytes.
</p>
-<codeblock rev="CDH-32135">
+<codeblock rev="">
[localhost:21000] > set mem_limit=3000000000;
MEM_LIMIT set to 3000000000
[localhost:21000] > select 5;
@@ -159,12 +159,12 @@ MEM_LIMIT set to 3mb
+---+
</codeblock>
- <p rev="CDH-32135">
+ <p rev="">
The following examples show how unrecognized <codeph>MEM_LIMIT</codeph>
values lead to errors for subsequent queries.
</p>
-<codeblock rev="CDH-32135">
+<codeblock rev="">
[localhost:21000] > set mem_limit=3tb;
MEM_LIMIT set to 3tb
[localhost:21000] > select 5;
@@ -177,7 +177,7 @@ Query: select 5
ERROR: Failed to parse query memory limit from 'xyz'.
</codeblock>
- <p rev="CDH-32135">
+ <p rev="">
The following examples shows the automatic query cancellation
when the <codeph>MEM_LIMIT</codeph> value is exceeded
on any host involved in the Impala query. First it runs a
@@ -187,7 +187,7 @@ ERROR: Failed to parse query memory limit from 'xyz'.
setting so that the same query cannot run.
</p>
-<codeblock rev="CDH-32135">
+<codeblock rev="">
[localhost:21000] > select count(*) from customer;
Query: select count(*) from customer
+----------+
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_operators.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_operators.xml b/docs/topics/impala_operators.xml
index 75b4461..126c2dc 100644
--- a/docs/topics/impala_operators.xml
+++ b/docs/topics/impala_operators.xml
@@ -778,7 +778,7 @@ select 'ABCXYZ' not like 'ab_xyz';
<codeph>WHERE 5 IN (id)</codeph> produce the same results.
</p>
- <p rev="CDH-40407">
+ <p rev="">
The set of values to check against can be specified as constants, function calls, column names, or other expressions in the query
text. The maximum number of expressions in the <codeph>IN</codeph> list is 9999. (The maximum number of elements of
a single expression is 10,000 items, and the <codeph>IN</codeph> operator itself counts as one.)
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_parquet.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_parquet.xml b/docs/topics/impala_parquet.xml
index e4f8a7f..81fdb69 100644
--- a/docs/topics/impala_parquet.xml
+++ b/docs/topics/impala_parquet.xml
@@ -1105,7 +1105,7 @@ select * from production_table where c1 = 100 and c2 < 50 and ...;
</li>
</ul>
- <p rev="2.6.0 IMPALA-2835 CDH-33330">
+ <p rev="2.6.0 IMPALA-2835">
You might find that you have Parquet files where the columns do not line up in the same
order as in your Impala table. For example, you might have a Parquet file that was part of
a table with columns <codeph>C1,C2,C3,C4</codeph>, and now you want to reuse the same
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/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 826839d..c9aa617 100644
--- a/docs/topics/impala_parquet_fallback_schema_resolution.xml
+++ b/docs/topics/impala_parquet_fallback_schema_resolution.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="parquet_fallback_schema_resolution" rev="2.6.0 IMPALA-2835 CDH-33330">
+<concept id="parquet_fallback_schema_resolution" rev="2.6.0 IMPALA-2835">
<title>PARQUET_FALLBACK_SCHEMA_RESOLUTION Query Option (<keyword keyref="impala26"/> or higher only)</title>
<titlealts audience="PDF"><navtitle>PARQUET_FALLBACK_SCHEMA_RESOLUTION</navtitle></titlealts>
@@ -35,7 +35,7 @@ under the License.
<conbody>
- <p rev="2.6.0 IMPALA-2835 CDH-33330">
+ <p rev="2.6.0 IMPALA-2835">
<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.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_partitioning.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_partitioning.xml b/docs/topics/impala_partitioning.xml
index 1f70d2b..b59c243 100644
--- a/docs/topics/impala_partitioning.xml
+++ b/docs/topics/impala_partitioning.xml
@@ -212,7 +212,7 @@ insert into weather <b>partition (year=2014, month=04, day)</b> select 'sunny',2
</concept>
- <concept id="partition_refresh" rev="2.7.0 IMPALA-1683 CDH-43732">
+ <concept id="partition_refresh" rev="2.7.0 IMPALA-1683">
<title>Refreshing a Single Partition</title>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_proxy.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_proxy.xml b/docs/topics/impala_proxy.xml
index 2f3a3f6..d8823a8 100644
--- a/docs/topics/impala_proxy.xml
+++ b/docs/topics/impala_proxy.xml
@@ -129,8 +129,8 @@ under the License.
Specify the host and port settings for each Impala node. These are the hosts that the load balancer will
choose from when relaying each Impala query. See <xref href="impala_ports.xml#ports"/> for when to use
port 21000, 21050, or another value depending on what type of connections you are load balancing.
- <note rev="CDH-30399">
- <p rev="CDH-30399">
+ <note rev="">
+ <p rev="">
In particular, if you are using Hue or JDBC-based applications,
you typically set up load balancing for both ports 21000 and 21050, because
these client applications connect through port 21050 while the <cmdname>impala-shell</cmdname>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_refresh.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_refresh.xml b/docs/topics/impala_refresh.xml
index 7897ecd..031bb2f 100644
--- a/docs/topics/impala_refresh.xml
+++ b/docs/topics/impala_refresh.xml
@@ -50,7 +50,7 @@ under the License.
<p conref="../shared/impala_common.xml#common/syntax_blurb"/>
-<codeblock rev="IMPALA-1683 CDH-43732">REFRESH [<varname>db_name</varname>.]<varname>table_name</varname> [PARTITION (<varname>key_col1</varname>=<varname>val1</varname> [, <varname>key_col2</varname>=<varname>val2</varname>...])]</codeblock>
+<codeblock rev="IMPALA-1683">REFRESH [<varname>db_name</varname>.]<varname>table_name</varname> [PARTITION (<varname>key_col1</varname>=<varname>val1</varname> [, <varname>key_col2</varname>=<varname>val2</varname>...])]</codeblock>
<p conref="../shared/impala_common.xml#common/usage_notes_blurb"/>
@@ -171,23 +171,23 @@ under the License.
delay later, for example if the next reference to the table is during a benchmark test.
</p>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
<b>Refreshing a single partition:</b>
</p>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
In <keyword keyref="impala27_full"/> and higher, the <codeph>REFRESH</codeph> statement can apply to a single partition at a time,
rather than the whole table. Include the optional <codeph>PARTITION (<varname>partition_spec</varname>)</codeph>
clause and specify values for each of the partition key columns.
</p>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
The following examples show how to make Impala aware of data added to a single partition, after data is loaded into
a partition's data directory using some mechanism outside Impala, such as Hive or Spark. The partition can be one that
Impala created and is already aware of, or a new partition created through Hive.
</p>
-<codeblock rev="IMPALA-1683 CDH-43732"><![CDATA[
+<codeblock rev="IMPALA-1683"><![CDATA[
impala> create table p (x int) partitioned by (y int);
impala> insert into p (x,y) values (1,2), (2,2), (2,1);
impala> show partitions p;
@@ -213,13 +213,13 @@ impala> select x from p where y=1;
]]>
</codeblock>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
The same applies for tables with more than one partition key column.
The <codeph>PARTITION</codeph> clause of the <codeph>REFRESH</codeph>
statement must include all the partition key columns.
</p>
-<codeblock rev="IMPALA-1683 CDH-43732"><![CDATA[
+<codeblock rev="IMPALA-1683"><![CDATA[
impala> create table p2 (x int) partitioned by (y int, z int);
impala> insert into p2 (x,y,z) values (0,0,0), (1,2,3), (2,2,3);
impala> show partitions p2;
@@ -246,14 +246,14 @@ impala> select x from p where y=2 and z = 3;
]]>
</codeblock>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
The following examples show how specifying a nonexistent partition does not cause any error,
and the order of the partition key columns does not have to match the column order in the table.
The partition spec must include all the partition key columns; specifying an incomplete set of
columns does cause an error.
</p>
-<codeblock rev="IMPALA-1683 CDH-43732"><![CDATA[
+<codeblock rev="IMPALA-1683"><![CDATA[
-- Partition doesn't exist.
refresh p2 partition (y=0, z=3);
refresh p2 partition (y=0, z=-1)
@@ -299,7 +299,7 @@ ERROR: AnalysisException: Items in partition spec must exactly match the partiti
</p>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have execute
permissions for all the relevant directories holding table data.
@@ -311,7 +311,7 @@ ERROR: AnalysisException: Items in partition spec must exactly match the partiti
but subsequent statements such as <codeph>SELECT</codeph>
or <codeph>SHOW TABLE STATS</codeph> could fail.
</p>
- <p rev="IMPALA-1683 CDH-43732">
+ <p rev="IMPALA-1683">
All HDFS and Sentry permissions and privileges are the same whether you refresh the entire table
or a single partition.
</p>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_runtime_bloom_filter_size.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_runtime_bloom_filter_size.xml b/docs/topics/impala_runtime_bloom_filter_size.xml
index 644dda7..62d0c03 100644
--- a/docs/topics/impala_runtime_bloom_filter_size.xml
+++ b/docs/topics/impala_runtime_bloom_filter_size.xml
@@ -41,13 +41,13 @@ under the License.
</p>
<note type="important">
- <p rev="2.6.0 CDH-41184 IMPALA-3007">
+ <p rev="2.6.0 IMPALA-3007">
In <keyword keyref="impala26_full"/> and higher, this query option only applies as a fallback, when statistics
are not available. By default, Impala estimates the optimal size of the Bloom filter structure
regardless of the setting for this option. (This is a change from the original behavior in
<keyword keyref="impala25_full"/>.)
</p>
- <p rev="2.6.0 CDH-41184 IMPALA-3007">
+ <p rev="2.6.0 IMPALA-3007">
In <keyword keyref="impala26_full"/> and higher, when the value of this query option is used for query planning,
it is constrained by the minimum and maximum sizes specified by the
<codeph>RUNTIME_FILTER_MIN_SIZE</codeph> and <codeph>RUNTIME_FILTER_MAX_SIZE</codeph> query options.
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_runtime_filter_max_size.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_runtime_filter_max_size.xml b/docs/topics/impala_runtime_filter_max_size.xml
index 6349437..7e86914 100644
--- a/docs/topics/impala_runtime_filter_max_size.xml
+++ b/docs/topics/impala_runtime_filter_max_size.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="runtime_filter_max_size" rev="2.6.0 IMPALA-3480 CDH-41184">
+<concept id="runtime_filter_max_size" rev="2.6.0 IMPALA-3480">
<title>RUNTIME_FILTER_MAX_SIZE Query Option (<keyword keyref="impala26"/> or higher only)</title>
<titlealts audience="PDF"><navtitle>RUNTIME_FILTER_MAX_SIZE</navtitle></titlealts>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_runtime_filter_min_size.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_runtime_filter_min_size.xml b/docs/topics/impala_runtime_filter_min_size.xml
index 9d673c2..c341b79 100644
--- a/docs/topics/impala_runtime_filter_min_size.xml
+++ b/docs/topics/impala_runtime_filter_min_size.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="runtime_filter_min_size" rev="2.6.0 IMPALA-3480 CDH-41184">
+<concept id="runtime_filter_min_size" rev="2.6.0 IMPALA-3480">
<title>RUNTIME_FILTER_MIN_SIZE Query Option (<keyword keyref="impala26"/> or higher only)</title>
<titlealts audience="PDF"><navtitle>RUNTIME_FILTER_MIN_SIZE</navtitle></titlealts>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_runtime_filter_mode.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_runtime_filter_mode.xml b/docs/topics/impala_runtime_filter_mode.xml
index 7797119..56bbf21 100644
--- a/docs/topics/impala_runtime_filter_mode.xml
+++ b/docs/topics/impala_runtime_filter_mode.xml
@@ -50,7 +50,7 @@ under the License.
or corresponding mnemonic strings (<codeph>OFF</codeph>, <codeph>LOCAL</codeph>, <codeph>GLOBAL</codeph>).
</p>
- <p rev="2.6.0 CDH-41184">
+ <p rev="2.6.0">
<b>Default:</b> 2 (equivalent to <codeph>GLOBAL</codeph>); formerly was 1 / <codeph>LOCAL</codeph>, in <keyword keyref="impala25_full"/>
</p>
@@ -58,13 +58,13 @@ under the License.
<p conref="../shared/impala_common.xml#common/usage_notes_blurb"/>
- <p rev="2.6.0 CDH-41184">
+ <p rev="2.6.0">
In <keyword keyref="impala26_full"/> and higher, the default is <codeph>GLOBAL</codeph>.
This setting is recommended for a wide variety of workloads, to provide best
performance with <q>out of the box</q> settings.
</p>
- <p rev="2.6.0 CDH-41184">
+ <p rev="2.6.0">
The lowest setting of <codeph>LOCAL</codeph> does a similar level of optimization
(such as partition pruning) as in earlier Impala releases.
This setting was the default in <keyword keyref="impala25_full"/>,
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_s3_skip_insert_staging.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_s3_skip_insert_staging.xml b/docs/topics/impala_s3_skip_insert_staging.xml
index 82e8ec5..879fe82 100644
--- a/docs/topics/impala_s3_skip_insert_staging.xml
+++ b/docs/topics/impala_s3_skip_insert_staging.xml
@@ -18,7 +18,7 @@ specific language governing permissions and limitations
under the License.
-->
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
-<concept id="s3_skip_insert_staging" rev="2.6.0 IMPALA-3452 CDH-39913">
+<concept id="s3_skip_insert_staging" rev="2.6.0 IMPALA-3452">
<title>S3_SKIP_INSERT_STAGING Query Option (<keyword keyref="impala26"/> or higher only)</title>
<titlealts audience="PDF"><navtitle>S3_SKIP_INSERT_STAGING</navtitle></titlealts>
@@ -36,7 +36,7 @@ under the License.
<conbody>
- <p rev="2.6.0 IMPALA-3452 CDH-39913">
+ <p rev="2.6.0 IMPALA-3452">
<indexterm audience="hidden">IMPALA_S3_SKIP_INSERT_STAGING query option</indexterm>
</p>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_scalability.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_scalability.xml b/docs/topics/impala_scalability.xml
index 588aa29..0ccf0c0 100644
--- a/docs/topics/impala_scalability.xml
+++ b/docs/topics/impala_scalability.xml
@@ -749,7 +749,7 @@ try to limit the number of partitions for any partitioned table to a few tens of
</conbody>
</concept>
-<concept rev="CDH-38321" id="kerberos_overhead_cluster_size">
+<concept rev="" id="kerberos_overhead_cluster_size">
<title>Kerberos-Related Network Overhead for Large Clusters</title>
<conbody>
<p>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_schedule_random_replica.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_schedule_random_replica.xml b/docs/topics/impala_schedule_random_replica.xml
index c104990..ae5978f 100644
--- a/docs/topics/impala_schedule_random_replica.xml
+++ b/docs/topics/impala_schedule_random_replica.xml
@@ -75,7 +75,7 @@ under the License.
which can further reduce the chance of CPU hotspots.
</p>
- <p rev="CDH-43739 IMPALA-2979">
+ <p rev="IMPALA-2979">
This query option works in conjunction with the work scheduling improvements
in <keyword keyref="impala25_full"/> and higher. The scheduling improvements
distribute the processing for cached HDFS data blocks to minimize hotspots:
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_select.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_select.xml b/docs/topics/impala_select.xml
index efd3e24..c28890a 100644
--- a/docs/topics/impala_select.xml
+++ b/docs/topics/impala_select.xml
@@ -179,7 +179,7 @@ LIMIT <i>expression</i> [OFFSET <i>expression</i>]
<p conref="../shared/impala_common.xml#common/cancel_blurb_yes"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have read
permissions for the files in all applicable directories in all source tables,
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_shell_commands.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_shell_commands.xml b/docs/topics/impala_shell_commands.xml
index a7b4c75..3469c15 100644
--- a/docs/topics/impala_shell_commands.xml
+++ b/docs/topics/impala_shell_commands.xml
@@ -328,7 +328,7 @@ under the License.
</p>
</entry>
</row>
- <row id="source_cmd" rev="IMPALA-3397 CDH-40097">
+ <row id="source_cmd" rev="IMPALA-3397">
<entry>
<p>
<codeph>source</codeph> or <codeph>src</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_shell_running_commands.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_shell_running_commands.xml b/docs/topics/impala_shell_running_commands.xml
index 4b89587..e74d015 100644
--- a/docs/topics/impala_shell_running_commands.xml
+++ b/docs/topics/impala_shell_running_commands.xml
@@ -189,12 +189,12 @@ Error: Unknown variable TNAME
+----------+
</codeblock>
- <p rev="IMPALA-3397 CDH-40097">
+ <p rev="IMPALA-3397">
The following example shows how the <codeph>SOURCE</codeph> command can execute
a series of statements from a file:
</p>
-<codeblock rev="IMPALA-3397 CDH-40097">
+<codeblock rev="IMPALA-3397">
$ cat commands.sql
show databases;
show tables in default;
@@ -234,7 +234,7 @@ Query: show functions in _impala_builtins like '*minute*'
Fetched 5 row(s) in 0.03s
</codeblock>
- <p rev="IMPALA-3397 CDH-40097">
+ <p rev="IMPALA-3397">
The following example shows how a file that is run by the <codeph>SOURCE</codeph> command,
or through the <codeph>-q</codeph> or <codeph>-f</codeph> options of <cmdname>impala-shell</cmdname>,
can contain additional <codeph>SOURCE</codeph> commands.
@@ -244,7 +244,7 @@ Fetched 5 row(s) in 0.03s
or test environments.
</p>
-<codeblock rev="IMPALA-3397 CDH-40097">
+<codeblock rev="IMPALA-3397">
$ cat nested1.sql
show functions in _impala_builtins like '*minute*';
source nested2.sql
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_string_functions.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_string_functions.xml b/docs/topics/impala_string_functions.xml
index 048daf4..98bf2ba 100644
--- a/docs/topics/impala_string_functions.xml
+++ b/docs/topics/impala_string_functions.xml
@@ -740,7 +740,7 @@ Returned 1 row(s) in 0.12s</codeblock>
</dlentry>
- <dlentry rev="2.3.0 CDH-35915 IMPALA-2084" id="split_part">
+ <dlentry rev="2.3.0 IMPALA-2084" id="split_part">
<dt>
<codeph>split_part(string source, string delimiter, bigint n)</codeph>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_troubleshooting.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_troubleshooting.xml b/docs/topics/impala_troubleshooting.xml
index 304f770..0dd499f 100644
--- a/docs/topics/impala_troubleshooting.xml
+++ b/docs/topics/impala_troubleshooting.xml
@@ -94,7 +94,7 @@ under the License.
</conbody>
</concept>
- <concept id="trouble_io" rev="CDH-19201">
+ <concept id="trouble_io" rev="">
<title>Troubleshooting I/O Capacity Problems</title>
<conbody>
<p>
http://git-wip-us.apache.org/repos/asf/incubator-impala/blob/f3820e62/docs/topics/impala_truncate_table.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_truncate_table.xml b/docs/topics/impala_truncate_table.xml
index e2de146..cf0e0a4 100644
--- a/docs/topics/impala_truncate_table.xml
+++ b/docs/topics/impala_truncate_table.xml
@@ -96,7 +96,7 @@ under the License.
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
<p conref="../shared/impala_common.xml#common/permissions_blurb"/>
- <p rev="CDH-19187">
+ <p rev="">
The user ID that the <cmdname>impalad</cmdname> daemon runs under,
typically the <codeph>impala</codeph> user, must have write
permission for all the files and directories that make up the table.