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

ASF GitHub Bot commented on PHOENIX-4424:
-----------------------------------------

GitHub user karanmehta93 opened a pull request:

    https://github.com/apache/phoenix/pull/284

    PHOENIX-4424 Allow users to create DEFAULT and HBASE Schema (Uppercas…

    …e Schema Names)
    
    @twdsilva Please review.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/karanmehta93/phoenix PHOENIX-4424

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/phoenix/pull/284.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #284
    
----
commit 1d745db801591ac1ca561ce3bc4b3b3f50dd2a8d
Author: Karan Mehta <[email protected]>
Date:   2017-12-01T01:25:20Z

    PHOENIX-4424 Allow users to create DEFAULT and HBASE Schema (Uppercase 
Schema Names)

----


> Allow users to create "DEFAULT" and "HBASE" Schema (Uppercase Schema Names)
> ---------------------------------------------------------------------------
>
>                 Key: PHOENIX-4424
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4424
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Karan Mehta
>            Assignee: Karan Mehta
>
> We currently block users to create "DEFAULT" and "HBASE" schema, however it 
> should be actually "default" and "hbase" since hbase namespace is case 
> sensitive. Hence we should update it and allow is users want to create 
> schema's with those names.
> If user wants to access the schema names with capital letters, they can pass 
> it in directly (Phoenix will automatically upper-case it) or pass it in 
> uppercase letters with double-quotes.
> FYI.
> [[email protected]]



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to