[
https://issues.apache.org/jira/browse/PHOENIX-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15447416#comment-15447416
]
Hudson commented on PHOENIX-1647:
---------------------------------
FAILURE: Integrated in Jenkins build Phoenix-master #1374 (See
[https://builds.apache.org/job/Phoenix-master/1374/])
PHOENIX-1647 Correctly return that Phoenix supports schema name (mujtaba: rev
d873c2ffd1e539ecd56858c82f0ba2d23e877cf9)
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
> 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)
