[
https://issues.apache.org/jira/browse/PHOENIX-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184805#comment-14184805
]
Hudson commented on PHOENIX-1366:
---------------------------------
SUCCESS: Integrated in Phoenix | Master #458 (See
[https://builds.apache.org/job/Phoenix-master/458/])
PHOENIX-1366 ORDINAL_POSITION incorrect for multi-tenant table over
tenant-specific connection (Bruno Dumon) (jtaylor: rev
53c1fd7884a5eeaecf882cb199f7a25acb2d8212)
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/TenantSpecificTablesDDLIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/jdbc/PhoenixDatabaseMetaData.java
> ORDINAL_POSITION incorrect for multi-tenant table over tenant-specific
> connection
> ---------------------------------------------------------------------------------
>
> Key: PHOENIX-1366
> URL: https://issues.apache.org/jira/browse/PHOENIX-1366
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0
> Reporter: James Taylor
> Attachments: PHOENIX-1366.patch
>
>
> We strip out the tenant ID column from our
> connection.getMetaData().getColumns() call for a multi-tenant table over a
> tenant-specific connection as of PHOENIX-1271. However, in doing so, we
> should adjust down the ORDINAL_POSITION by one for every column *after* the
> tenant ID column.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
