[
https://issues.apache.org/jira/browse/PHOENIX-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14143397#comment-14143397
]
James Taylor commented on PHOENIX-1271:
---------------------------------------
+1 to the idea. It's a bit tricky to implement, though, because the query is
run over only columns, not table rows, and the column rows do not know whether
the table is multi-tenant. Here are some solutions I can think of:
- store isMultiTenant attribute on the tenantID column (it's only on the table
row currently).
- do a self join to the table row for the column query (maybe overkill?)
- don't filter table rows on the column query, but filter then client-side
maintaining a bit of state to use for the columns that will follow in the
result set.
> 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)
