[
https://issues.apache.org/jira/browse/PHOENIX-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158110#comment-14158110
]
Bruno Dumon commented on PHOENIX-1271:
--------------------------------------
I tried to work around this in my code by wrapping the ResultSet returned from
DatabaseMetaData.getColumns() with a ResultSet that drops the tenant id column.
I will attach the code for this. If such a solution would be acceptable for
Phoenix, I can look into preparing a patch.
> Column metadata doesn't hide tenant column on tenant-specific connections.
> --------------------------------------------------------------------------
>
> Key: PHOENIX-1271
> URL: https://issues.apache.org/jira/browse/PHOENIX-1271
> Project: Phoenix
> Issue Type: Bug
> Reporter: Karel Vervaeke
>
> connection.getMetaData().getColumns(...) always returns all columns.
> For multi-tenant tables it would make more sense if the first PK (the
> tenant-id column) would be excluded. If we do this the number of columns
> returned would match the number of columns you get when executing a "select
> *" query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
