[DOCS] Fixed an inconsistent table ordering recommendations with STRAIGHT_JOIN
Change-Id: I9ff2245b6d8e3160a10aae64f622813a40121ee8 Reviewed-on: http://gerrit.cloudera.org:8080/10519 Reviewed-by: Tim Armstrong <[email protected]> Tested-by: Impala Public Jenkins <[email protected]> Project: http://git-wip-us.apache.org/repos/asf/impala/repo Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/2f22a6f6 Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/2f22a6f6 Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/2f22a6f6 Branch: refs/heads/master Commit: 2f22a6f67ff363a0832a7ceee5d0020c8fd9b15a Parents: e4c52e3 Author: Alex Rodoni <[email protected]> Authored: Fri May 25 13:14:24 2018 -0700 Committer: Impala Public Jenkins <[email protected]> Committed: Wed May 30 17:50:04 2018 +0000 ---------------------------------------------------------------------- docs/topics/impala_perf_joins.xml | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/impala/blob/2f22a6f6/docs/topics/impala_perf_joins.xml ---------------------------------------------------------------------- diff --git a/docs/topics/impala_perf_joins.xml b/docs/topics/impala_perf_joins.xml index 05dadbb..60c7b62 100644 --- a/docs/topics/impala_perf_joins.xml +++ b/docs/topics/impala_perf_joins.xml @@ -85,13 +85,13 @@ under the License. <li> Join the next smallest table, then the next smallest, and so on. </li> + </ul> - <li> + <p> For example, if you had tables <codeph>BIG</codeph>, <codeph>MEDIUM</codeph>, <codeph>SMALL</codeph>, and <codeph>TINY</codeph>, the logical join order to try would be <codeph>BIG</codeph>, <codeph>TINY</codeph>, <codeph>SMALL</codeph>, <codeph>MEDIUM</codeph>. - </li> - </ul> + </p> <p> The terms <q>largest</q> and <q>smallest</q> refers to the size of the intermediate result set based on the @@ -153,8 +153,7 @@ under the License. immediately after the <codeph>SELECT</codeph> and any <codeph>DISTINCT</codeph> or <codeph>ALL</codeph> keywords. The <codeph>STRAIGHT_JOIN</codeph> keyword turns off the reordering of join clauses that Impala does internally, and produces a plan that relies on the join - clauses being ordered optimally in the query text. In this case, rewrite the query so that the largest - table is on the left, followed by the next largest, and so on until the smallest table is on the right. + clauses being ordered optimally in the query text. </p> <note>
