You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ta...@apache.org on 2019/02/16 01:20:54 UTC
[impala] 04/11: [DOCS] Wording changes in DPP examples for clarity
This is an automated email from the ASF dual-hosted git repository.
tarmstrong pushed a commit to branch 2.x
in repository https://gitbox.apache.org/repos/asf/impala.git
commit 6bfa7202c224ed4360a371a820ae2429ef0b2f0d
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Thu Jun 14 13:13:10 2018 -0700
[DOCS] Wording changes in DPP examples for clarity
Change-Id: If786fc3d3064b26b213afb685a2f310cebe904fe
Reviewed-on: http://gerrit.cloudera.org:8080/10718
Reviewed-by: Alex Rodoni <ar...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
---
docs/shared/impala_common.xml | 9 ++++-----
docs/topics/impala_partitioning.xml | 6 ++++--
docs/topics/impala_runtime_filtering.xml | 5 ++---
3 files changed, 10 insertions(+), 10 deletions(-)
diff --git a/docs/shared/impala_common.xml b/docs/shared/impala_common.xml
index 38a7b96..613f5ee 100644
--- a/docs/shared/impala_common.xml
+++ b/docs/shared/impala_common.xml
@@ -1808,9 +1808,8 @@ INSERT INTO yy2 VALUES ('1999', 1999), ('2000', 2000), ('2001', 2001);
COMPUTE STATS yy2;
-- The following query reads an unknown number of partitions, whose key values
--- are only known at run time. The 'runtime filters' lines show how the
--- information about the partitions is calculated in query fragment 02, and then
--- used in query fragment 00 to decide which partitions to skip.
+-- are only known at run time. The <b>runtime filters</b> line shows the
+-- information used in query fragment 02 to decide which partitions to skip.
EXPLAIN SELECT s FROM yy WHERE year IN (SELECT year FROM yy2);
+--------------------------------------------------------------------------+
@@ -1820,7 +1819,7 @@ EXPLAIN SELECT s FROM yy WHERE year IN (SELECT year FROM yy2);
| | |
| 02:HASH JOIN [LEFT SEMI JOIN, BROADCAST] |
| | hash predicates: year = year |
-| | <b>runtime filters: RF000 <- year</b> |
+| | <b>runtime filters: RF000 <- year</b> |
| | |
| |--03:EXCHANGE [BROADCAST] |
| | | |
@@ -1828,7 +1827,7 @@ EXPLAIN SELECT s FROM yy WHERE year IN (SELECT year FROM yy2);
| | partitions=1/1 files=1 size=620B |
| | |
| 00:SCAN HDFS [default.yy] |
-| <b>partitions=5/5</b> files=5 size=1.71KB |
+| <b>partitions=5/5</b> files=5 size=1.71KB |
| runtime filters: RF000 -> year |
+--------------------------------------------------------------------------+
diff --git a/docs/topics/impala_partitioning.xml b/docs/topics/impala_partitioning.xml
index 011ff88..5a986f6 100644
--- a/docs/topics/impala_partitioning.xml
+++ b/docs/topics/impala_partitioning.xml
@@ -440,9 +440,11 @@ SELECT COUNT(*) FROM sales_table WHERE year IN (2005, 2010, 2015);
indicating that static partition pruning will not happen.
</p>
- <p>The Filter summary in the <codeph>PROFILE</codeph> output shows that
+ <p>
+ The Filter summary in the <codeph>PROFILE</codeph> output shows that
the scan node filtered out based on a runtime filter of dynamic
- partition pruning. </p>
+ partition pruning.
+ </p>
<codeblock>Filter 0 (1.00 MB):
- Files processed: 3
diff --git a/docs/topics/impala_runtime_filtering.xml b/docs/topics/impala_runtime_filtering.xml
index cce9155..d496098 100644
--- a/docs/topics/impala_runtime_filtering.xml
+++ b/docs/topics/impala_runtime_filtering.xml
@@ -345,9 +345,8 @@ under the License.
<p>
The following example shows a query that uses a single runtime filter,
- labeled <codeph>RF000</codeph>, to prune the partitions that are scanned
- in one stage of the query, based on evaluating the result set of a
- subquery:
+ labeled <codeph>RF000</codeph>, to prune the partitions based on
+ evaluating the result set of a subquery at runtime:
</p>
<codeblock conref="../shared/impala_common.xml#common/simple_dpp_example"/>