You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by jo...@apache.org on 2019/09/13 00:07:10 UTC

[impala] branch master updated: IMPALA-8548: [DOCS] Impala supports ordinal substitutions in SELECT

This is an automated email from the ASF dual-hosted git repository.

joemcdonnell pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git


The following commit(s) were added to refs/heads/master by this push:
     new 54c1957  IMPALA-8548: [DOCS] Impala supports ordinal substitutions in SELECT
54c1957 is described below

commit 54c1957f134710fdc75753a4255d99dd0c6f67ba
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Tue Sep 10 16:42:23 2019 -0700

    IMPALA-8548: [DOCS] Impala supports ordinal substitutions in SELECT
    
    Change-Id: Ia48a4a6711ffcf326f3f51200040420101451967
    Reviewed-on: http://gerrit.cloudera.org:8080/14209
    Tested-by: Impala Public Jenkins <im...@cloudera.com>
    Reviewed-by: Zoltan Borok-Nagy <bo...@cloudera.com>
---
 docs/shared/impala_common.xml | 15 ++++++++-------
 docs/topics/impala_select.xml | 17 +++--------------
 2 files changed, 11 insertions(+), 21 deletions(-)

diff --git a/docs/shared/impala_common.xml b/docs/shared/impala_common.xml
index dcc74f4..6d96090 100644
--- a/docs/shared/impala_common.xml
+++ b/docs/shared/impala_common.xml
@@ -1098,12 +1098,13 @@ select concat('abc','mno','xyz');</codeblock>
 </codeblock>
       </p>
 
-      <p id="column_ordinals" rev="IMPALA-6415 IMPALA-5191">
-        You can also refer to <codeph>SELECT</codeph>-list items by their ordinal position.
-        Impala supports ordinals in the <codeph>GROUP BY</codeph>, <codeph>HAVING</codeph>, and
-        <codeph>ORDER BY</codeph> clauses. From Impala 3.0, ordinals can only be used at the top
-        level. For example, the following statements are allowed:
-<codeblock>
+      <p id="column_ordinals" rev="IMPALA-6415 IMPALA-5191"> You can refer to
+          <codeph>SELECT</codeph>-list items by their ordinal position. Impala
+        supports ordinals in the <codeph>GROUP BY</codeph>,
+          <codeph>HAVING</codeph>, and <codeph>ORDER BY</codeph> clauses. From
+        Impala 3.0, ordinals can only be used at the top level. For example, the
+        following statements are allowed:
+        <codeblock>
   SELECT int_col / 2, sum(x)
   FROM t
   GROUP BY 1;
@@ -1118,7 +1119,7 @@ select concat('abc','mno','xyz');</codeblock>
   HAVING 1;
 </codeblock>
         Numbers in subexpressions are not interpreted as ordinals:
-<codeblock>
+        <codeblock>
   SELECT int_col / 2, sum(x)
   FROM t
   GROUP BY 1 * 2;
diff --git a/docs/topics/impala_select.xml b/docs/topics/impala_select.xml
index 7b516a7..cddb00a 100644
--- a/docs/topics/impala_select.xml
+++ b/docs/topics/impala_select.xml
@@ -124,6 +124,9 @@ table_reference := { <varname>table_name</varname> | (<varname>subquery</varname
         restriction is lifted; sort operations that would exceed the Impala memory limit automatically use a
         temporary disk work area to perform the sort.
       </li>
+      <li>
+        <p conref="../shared/impala_common.xml#common/column_ordinals"/>
+      </li>
 
       <li>
         <p conref="../shared/impala_common.xml#common/join_types"/>
@@ -210,18 +213,4 @@ table_reference := { <varname>table_name</varname> | (<varname>subquery</varname
       details.
     </p>
   </conbody>
-
-  <concept id="where" audience="hidden">
-
-<!-- WHERE hidden for the moment until there's the chance to add some reasonably comprehensive content
-
-     and make it its own file. -->
-
-    <title>WHERE Clause</title>
-
-    <conbody>
-
-      <p/>
-    </conbody>
-  </concept>
 </concept>