[jira] [Commented] (PHOENIX-1647) Fully qualified tablename query support in Phoenix

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

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

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

GitHub user kliewkliew opened a pull request:

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

    PHOENIX-1647 Fully qualified tablename query support in Phoenix

    

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

    $ git pull https://github.com/kliewkliew/phoenix PHOENIX-1647

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

    https://github.com/apache/phoenix/pull/204.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 #204
    
----

----


> Fully qualified tablename query support in Phoenix
> --------------------------------------------------
>
>                 Key: PHOENIX-1647
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1647
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.1.1
>         Environment: Phoenix driver 4.1.1
> HBase 98.9
> Hadoop 2
>            Reporter: suraj misra
>              Labels: Newbie
>             Fix For: 4.9.0
>
>
> I am able to execute queries having fully qualified names in table names. For example:
> UPSERT INTO TEST.CUSTOMERS_TEST VALUES(102,'hbase2',20,'del')
> But when I look at the phoenix driver implementation, I can see that implementation for DatabaseMetaData .supportsSchemasInDataManipulation method always return false.
> As per JDBC documentation, this method retrieves whether a schema name can be used in a data manipulation statement.But as you can see in above example, I can execute DML statements with schema names as well along with other statements. 
> Could someone please let me know if there is any specific reason to keep it as false. 



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