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 2018/03/27 18:47:23 UTC

[3/3] impala git commit: IMPALA-6510: [DOCS] Remove refresh_after_connect

IMPALA-6510: [DOCS] Remove refresh_after_connect

Removed refresh_after_connect option from impala shell options.
Removed the refresh_after_connect from INVALIDATE METADATA doc.

Cherry-picks: not for 2.x
Change-Id: I7bd49cb32a952362dcefc230d8feb1a7d6c13ea0
Reviewed-on: http://gerrit.cloudera.org:8080/9813
Reviewed-by: Tim Armstrong <ta...@cloudera.com>
Tested-by: Impala Public Jenkins


Project: http://git-wip-us.apache.org/repos/asf/impala/repo
Commit: http://git-wip-us.apache.org/repos/asf/impala/commit/b5dcc031
Tree: http://git-wip-us.apache.org/repos/asf/impala/tree/b5dcc031
Diff: http://git-wip-us.apache.org/repos/asf/impala/diff/b5dcc031

Branch: refs/heads/master
Commit: b5dcc031f75b2faff00d29616d83feedcb91c812
Parents: ee1b0fc
Author: Alex Rodoni <ar...@cloudera.com>
Authored: Mon Mar 26 18:15:52 2018 -0700
Committer: Impala Public Jenkins <im...@gerrit.cloudera.org>
Committed: Tue Mar 27 18:39:33 2018 +0000

----------------------------------------------------------------------
 docs/topics/impala_invalidate_metadata.xml |  8 --------
 docs/topics/impala_shell_options.xml       | 21 ---------------------
 2 files changed, 29 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/impala/blob/b5dcc031/docs/topics/impala_invalidate_metadata.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_invalidate_metadata.xml b/docs/topics/impala_invalidate_metadata.xml
index ddd79d5..d28e051 100644
--- a/docs/topics/impala_invalidate_metadata.xml
+++ b/docs/topics/impala_invalidate_metadata.xml
@@ -164,14 +164,6 @@ under the License.
       combination of Impala and Hive operations, see <xref href="impala_tutorial.xml#tutorial_impala_hive"/>.
     </p>
 
-    <p>
-      If you need to ensure that the metadata is up-to-date when you start an <cmdname>impala-shell</cmdname>
-      session, run <cmdname>impala-shell</cmdname> with the <codeph>-r</codeph> or
-      <codeph>--refresh_after_connect</codeph> command-line option. Because this operation adds a delay to the next
-      query against each table, potentially expensive for large tables with many partitions, try to avoid using
-      this option for day-to-day operations in a production environment.
-    </p>
-
     <p conref="../shared/impala_common.xml#common/permissions_blurb"/>
     <p rev="">
       The user ID that the <cmdname>impalad</cmdname> daemon runs under,

http://git-wip-us.apache.org/repos/asf/impala/blob/b5dcc031/docs/topics/impala_shell_options.xml
----------------------------------------------------------------------
diff --git a/docs/topics/impala_shell_options.xml b/docs/topics/impala_shell_options.xml
index 43e8162..d0407c9 100644
--- a/docs/topics/impala_shell_options.xml
+++ b/docs/topics/impala_shell_options.xml
@@ -410,27 +410,6 @@ under the License.
             <row>
               <entry>
                 <p>
-                  -r or --refresh_after_connect
-                </p>
-              </entry>
-              <entry rev="2.0.0">
-                <p>
-                  refresh_after_connect=true
-                </p>
-              </entry>
-              <entry>
-                <p>
-                  Updates Impala metadata upon connection. Same as running the
-                  <codeph><xref href="impala_invalidate_metadata.xml#invalidate_metadata">INVALIDATE
-                  METADATA</xref></codeph> statement after connecting. (This option was originally named when the
-                  <codeph>REFRESH</codeph> statement did the extensive metadata updates now performed by
-                  <codeph>INVALIDATE METADATA</codeph>.)
-                </p>
-              </entry>
-            </row>
-            <row>
-              <entry>
-                <p>
                   -d <varname>default_db</varname> or --database=<varname>default_db</varname>
                 </p>
               </entry>