mirror of
https://github.com/apache/impala.git
synced 2025-12-23 21:08:39 -05:00
8377b9949c
For this change to land in master, the audience="hidden" code review needs to be completed first. Otherwise, the doc build would still work but the audience="hidden" content would be visible rather than hidden as desired. Some work happening in parallel might introduce additional instances of audience="Cloudera". I suggest addressing those in a followup CR so this global change can land quickly. Since the changes apply across so many different files, but are so narrow in scope, I suggest that the way to validate (check that no extraneous changes were introduced accidentally) is to diff just the changed lines: git diff -U0 HEAD^ HEAD In patch set 2, I updated other topics marked audience="Cloudera" by CRs that were pushed in the meantime. Change-Id: Ic93d89da77e1f51bbf548a522d98d0c4e2fb31c8 Reviewed-on: http://gerrit.cloudera.org:8080/5613 Reviewed-by: John Russell <jrussell@cloudera.com> Tested-by: Impala Public Jenkins
98 lines
3.8 KiB
XML
98 lines
3.8 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<!--
|
|
Licensed to the Apache Software Foundation (ASF) under one
|
|
or more contributor license agreements. See the NOTICE file
|
|
distributed with this work for additional information
|
|
regarding copyright ownership. The ASF licenses this file
|
|
to you under the Apache License, Version 2.0 (the
|
|
"License"); you may not use this file except in compliance
|
|
with the License. You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing,
|
|
software distributed under the License is distributed on an
|
|
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
|
|
KIND, either express or implied. See the License for the
|
|
specific language governing permissions and limitations
|
|
under the License.
|
|
-->
|
|
<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
|
|
<concept id="use">
|
|
|
|
<title>USE Statement</title>
|
|
<titlealts audience="PDF"><navtitle>USE</navtitle></titlealts>
|
|
<prolog>
|
|
<metadata>
|
|
<data name="Category" value="Impala"/>
|
|
<data name="Category" value="SQL"/>
|
|
<data name="Category" value="Databases"/>
|
|
<data name="Category" value="Developers"/>
|
|
<data name="Category" value="Data Analysts"/>
|
|
</metadata>
|
|
</prolog>
|
|
|
|
<conbody>
|
|
|
|
<p>
|
|
<indexterm audience="hidden">USE statement</indexterm>
|
|
Switches the current session to a specified database. The <term>current database</term> is where any
|
|
<codeph>CREATE TABLE</codeph>, <codeph>INSERT</codeph>, <codeph>SELECT</codeph>, or other statements act when
|
|
you specify a table or other object name, without prefixing it with a database name. The new current database
|
|
applies for the duration of the session or unti another <codeph>USE</codeph> statement is executed.
|
|
</p>
|
|
|
|
<p conref="../shared/impala_common.xml#common/syntax_blurb"/>
|
|
|
|
<codeblock>USE <varname>db_name</varname></codeblock>
|
|
|
|
<p>
|
|
By default, when you connect to an Impala instance, you begin in a database named <codeph>default</codeph>.
|
|
</p>
|
|
|
|
<p conref="../shared/impala_common.xml#common/usage_notes_blurb"/>
|
|
|
|
<p>
|
|
Switching the default database is convenient in the following situations:
|
|
</p>
|
|
|
|
<ul>
|
|
<li>
|
|
To avoid qualifying each reference to a table with the database name. For example, <codeph>SELECT * FROM t1
|
|
JOIN t2</codeph> rather than <codeph>SELECT * FROM db.t1 JOIN db.t2</codeph>.
|
|
</li>
|
|
|
|
<li>
|
|
To do a sequence of operations all within the same database, such as creating a table, inserting data, and
|
|
querying the table.
|
|
</li>
|
|
</ul>
|
|
|
|
<p>
|
|
To start the <cmdname>impala-shell</cmdname> interpreter and automatically issue a <codeph>USE</codeph>
|
|
statement for a particular database, specify the option <codeph>-d <varname>db_name</varname></codeph> for
|
|
the <cmdname>impala-shell</cmdname> command. The <codeph>-d</codeph> option is useful to run SQL scripts,
|
|
such as setup or test scripts, against multiple databases without hardcoding a <codeph>USE</codeph> statement
|
|
into the SQL source.
|
|
</p>
|
|
|
|
<p conref="../shared/impala_common.xml#common/example_blurb"/>
|
|
|
|
<p>
|
|
See <xref href="impala_create_database.xml#create_database"/> for examples covering <codeph>CREATE
|
|
DATABASE</codeph>, <codeph>USE</codeph>, and <codeph>DROP DATABASE</codeph>.
|
|
</p>
|
|
|
|
<p conref="../shared/impala_common.xml#common/cancel_blurb_no"/>
|
|
|
|
<p conref="../shared/impala_common.xml#common/permissions_blurb_no"/>
|
|
|
|
<p conref="../shared/impala_common.xml#common/related_info"/>
|
|
|
|
<p>
|
|
<xref href="impala_create_database.xml#create_database"/>,
|
|
<xref href="impala_drop_database.xml#drop_database"/>, <xref href="impala_show.xml#show_databases"/>
|
|
</p>
|
|
</conbody>
|
|
</concept>
|