blob: 9a64c0b66b76b54695212ff391b33b6bd6a00c88 [file] [log] [blame]
////
/**
* @@@ START COPYRIGHT @@@
*
* 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.
*
* @@@ END COPYRIGHT @@@
*/
////
[[schema-controls]]
= Schema Controls
This section describes CQDs that are used for schema controls.
[[catalog]]
== Catalog
[cols="25%h,75%"]
|===
| *Description* | Specifies the default catalog name for all DDL and DML statements.
| *Values* | Any valid ANSI name, including delimited names. +
+
The default is *'TRAFODION'*.
| *Usage* | {project-name} tables must be in a catalog called TRAFODION. If you mostly access Hive or native HBase tables,
then the catalog could be changed to HIVE or HBASE respectively. +
+
The default setting is overridden by any catalog name specified in a SQL statement.
| *Production Usage* | Yes.
| *Impact* | Not applicable.
| *Level* | Any.
| *Conflicts/Synergies* | Alternately you can use the SET CATALOG statement.
| *Real Problem Addressed* | Not applicable.
| *Introduced In Release* | {project-name} 1.3.0.
| *Deprecated In Release* | Not applicable.
|===
<<<
[[schema]]
== Schema
[cols="25%h,75%"]
|===
| *Description* | Sets the default schema for the session.
| *Values* | SQL identifier. +
+
The default is *'TRAFODION'*.
| *Usage* | A SET SCHEMA statement or a CONTROL QUERY DEFAULT SCHEMA statement can be used to override the default schema name.
| *Production Usage* | It is a convenience so you do not have to type in two-part names.
| *Impact* | Not applicable.
| *Level* | Any.
| *Conflicts/Synergies* | Alternately you can use the SET SCHEMA statement.
| *Real Problem Addressed* | Not applicable.
| *Introduced In Release* | {project-name} 1.3.0.
| *Deprecated In Release* | Not applicable.
|===