[
https://issues.apache.org/jira/browse/PHOENIX-1416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309506#comment-14309506
]
James Taylor commented on PHOENIX-1416:
---------------------------------------
Ah, sorry - my mistake. This fix will appear in the 4.3 release.
> Given a schema name, DatabaseMetadata.getTables and getColumns calls
> erroneously match tables without schema
> -------------------------------------------------------------------------------------------------------------
>
> Key: PHOENIX-1416
> URL: https://issues.apache.org/jira/browse/PHOENIX-1416
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: Any unix or windows platform
> Reporter: Sergio Lob
> Assignee: James Taylor
> Fix For: 4.3, 4.2.1, 3.2.1, 3.3.
>
> Attachments: PHOENIX-1416.patch
>
>
> When calling DatabaseMetadata.getTables and getColumns to find a table
> defined with a particular schema, the Phoenix JDBC driver also returns
> description of a table with the same tablename, but empty schema.
> eg, calling getTables(null, "R729999D", TABLE1, "TABLE");
> matches tables R729999D.TABLE1 and TABLE1 (no schema). It should return
> information on only table R729999D.TABLE1.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
