You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Ankit Singhal (JIRA)" <ji...@apache.org> on 2016/04/14 11:57:25 UTC

[jira] [Commented] (PHOENIX-2571) Support specifying a default schema

    [ https://issues.apache.org/jira/browse/PHOENIX-2571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15240890#comment-15240890 ] 

Ankit Singhal commented on PHOENIX-2571:
----------------------------------------

Now default schema can be set in connection with any of the following ways.

* jdbc url
{code}
localhost;schema=TEST_SCHEMA
{code}
* property in configuration
{code}
<property>
<name>phoenix.connection.schema</name>
<value>TEST_SCHEMA</value>
</property>
{code}
* USE <SCHEMA> construct
{code}
USE TEST_SCHEMA //to set TEST_SCHEMA as default schema for connection.
USE DEFAULT //to unset schema for connection.
{code}



> Support specifying a default schema
> -----------------------------------
>
>                 Key: PHOENIX-2571
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2571
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Ankit Singhal
>             Fix For: 4.8.0
>
>
> Based on idea from comment in PHOENIX-1966. If we can provide a means of setting the default schema (either in a hbase-site.xml config file or through a new SQL statement), then we can provide a simple means of having different HBase namespaces. We want to be careful that this functionality won't conflict with PHOENIX-1311 which is a bigger effort than this one.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)