You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Amanchi Venkata Subbarayudu (JIRA)" <ji...@apache.org> on 2017/03/23 07:12:41 UTC
[jira] [Updated] (PHOENIX-3750) Phoenix Namespace : DDL statements
support
[ https://issues.apache.org/jira/browse/PHOENIX-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amanchi Venkata Subbarayudu updated PHOENIX-3750:
-------------------------------------------------
Description:
Starting from v4.8.0, phoenix enables to specify a schema to connect to, and all the DML/DDL operations performed are executed within the respective schema.
As of now, it seems that only supported DDL command is CREATE , i.e.
Assuming schema is set using one of the below
a. JDBC URL = localhost;schema=TSCHEMA
b. HBASE-CONFIG: with property phoenix.connection.schema=TSCHEMA
c. by logging into sqlline utility, and with command "USE TSCHEMA"
then..executing
>> CREATE TABLE command, create a table in TSCHEMA
>> CREATE VIEW, creates view in TSCHEMA
but, other DDL statements like
>> DROP TABLE
>> DROP VIEW etc. are checking for the tables/views in the default schema, rather than in TSCHEMA
thereby , these DROP commands to be executed by specifying TSCHEMA.<TABLE/VIEW> inplace of table/view.
Shoun't DROP,ALTER ddl-statements supposed to operate in the schema (TSCHEMA) provided?
was:
Starting from v4.8.0, phoenix enables to specify a schema to connect to, and all the DML operations performed are executed with respective schema tables.
As of now, it seems that only supported DDL command is CREATE operation with schema support, i.e.
Assuming schema is set using one of the below
a. JDBC URL = localhost;schema=TSCHEMA
b. HBASE-CONFIG: with property phoenix.connection.schema=TSCHEMA
c. by logging into sqlline utility, and with command "USE TSCHEMA"
then..executing
>> CREATE TABLE command, create a table in TSCHEMA
>> CREATE VIEW, creates view in TSCHEMA
but, other DDL statments like
>> DROP TABLE
>> DROP VIEW etc. are checking for the tables/views in the default schema, rather than in TSCHEMA
thereby , these DROP commands to be executed by specifying TSCHEMA.<TABLE/VIEW> inplace of table/view.
Shoun't DROP,ALTER ddl-statements operate in the schema (TSCHEMA) provided?
> Phoenix Namespace : DDL statements support
> ------------------------------------------
>
> Key: PHOENIX-3750
> URL: https://issues.apache.org/jira/browse/PHOENIX-3750
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.8.0, 4.8.1
> Reporter: Amanchi Venkata Subbarayudu
>
> Starting from v4.8.0, phoenix enables to specify a schema to connect to, and all the DML/DDL operations performed are executed within the respective schema.
> As of now, it seems that only supported DDL command is CREATE , i.e.
> Assuming schema is set using one of the below
> a. JDBC URL = localhost;schema=TSCHEMA
> b. HBASE-CONFIG: with property phoenix.connection.schema=TSCHEMA
> c. by logging into sqlline utility, and with command "USE TSCHEMA"
> then..executing
> >> CREATE TABLE command, create a table in TSCHEMA
> >> CREATE VIEW, creates view in TSCHEMA
> but, other DDL statements like
> >> DROP TABLE
> >> DROP VIEW etc. are checking for the tables/views in the default schema, rather than in TSCHEMA
> thereby , these DROP commands to be executed by specifying TSCHEMA.<TABLE/VIEW> inplace of table/view.
> Shoun't DROP,ALTER ddl-statements supposed to operate in the schema (TSCHEMA) provided?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)