phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (PHOENIX-1647) Fully qualified tablename query support in Phoenix
Date Mon, 29 Aug 2016 19:24:20 GMT

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

James Taylor commented on PHOENIX-1647:
---------------------------------------

[~mujtabachohan] - would you mind committing this on behalf of [~kliew]?

> 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
>            Assignee: Kevin Liew
>              Labels: Newbie
>             Fix For: 4.9.0, 4.8.1
>
>
> 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)

Mime
View raw message