You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "James Taylor (JIRA)" <ji...@apache.org> on 2016/08/29 19:25:20 UTC
[jira] [Updated] (PHOENIX-1647) Correctly return that Phoenix
supports schema name references in DatabaseMetaData
[ https://issues.apache.org/jira/browse/PHOENIX-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Taylor updated PHOENIX-1647:
----------------------------------
Summary: Correctly return that Phoenix supports schema name references in DatabaseMetaData (was: Fully qualified tablename query support in Phoenix)
> Correctly return that Phoenix supports schema name references in DatabaseMetaData
> ---------------------------------------------------------------------------------
>
> 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)