[
https://issues.apache.org/jira/browse/PHOENIX-1420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203261#comment-14203261
]
Hudson commented on PHOENIX-1420:
---------------------------------
SUCCESS: Integrated in Phoenix-3.0-hadoop1 #310 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/310/])
PHOENIX-1420 DatabaseMetaData.getschemas returns incorrect column order
(jtaylor: rev b5012d994278982c287b18b9051616cd76ac8b80)
*
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/QueryDatabaseMetaDataIT.java
> DatabaseMetaData.getschemas returns incorrect column order
> ----------------------------------------------------------
>
> Key: PHOENIX-1420
> URL: https://issues.apache.org/jira/browse/PHOENIX-1420
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.1
> Environment: all OS
> Reporter: Sergio Lob
> Attachments: PHOENIX-1420.patch
>
>
> DatabaseMetaData.getSchemas returns incorrect column order. According to java
> 6 api doc, getSchemas should return answer set columns in the following
> order:
>
> 1.TABLE_SCHEM String => schema name
> 2.TABLE_CATALOG String => catalog name
> The Phoenix JDBC driver returns these in reverse column order, i.e.
> 1. TABLE_CATALOG
> 2. TABLE_SCHEM
> Our experience with other JDBC drivers is that they return the data w/
> TABLE_SCHEM being the first column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
