[
https://issues.apache.org/jira/browse/PHOENIX-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158268#comment-14158268
]
James Taylor commented on PHOENIX-1271:
---------------------------------------
I like the concept, [~bruno]. Couple of ideas that might reduce the amount of
code. How about either?
- Creating a derived class from DelegateIterator that more or less does what
you're doing in the next method. Then try using
PhoenixConnection.createStatement(PhoenixStatementFactory), our backdoor API,
to implement your own PhoenixStatementFactory to to get a PhoenixStatement
that overrides newResultSet that instantiates a PhoenixResultSet that delegate
to your DelegateIterator (i.e. wrapping the one you'd normally get).
- Or if this doesn't work well, create a DelegateResultIterator class and then
have your class derive from it in case others need a delegate too?
> 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
> Attachments: TenantColumnFilteringResultSet.java
>
>
> 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)
