[
https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549420#comment-15549420
]
Maryann Xue commented on PHOENIX-2679:
--------------------------------------
The shadow tables are actually what represent the real table structure in
HBase, but they have tweaked names, just to be different from the original
table names. In order not to let users access those made-up names in SQL
queries, I just add those tables in a later stage after validation, but before
planning.
Actually I made a mistake in the above comment. The test case can now pass even
with a filter in the query. As long as "flattenTypes()" works OK, our shadow
table replacement rule can work too. So right now the problem is just (1)
flatten types and (2) disable field trimming at that stage. We can actually
apply a field trimming program after shadow table replacement program.
> Implement column family schema structure in Calcite-Phoenix
> -----------------------------------------------------------
>
> Key: PHOENIX-2679
> URL: https://issues.apache.org/jira/browse/PHOENIX-2679
> Project: Phoenix
> Issue Type: Task
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Labels: calcite
> Attachments: PHOENIX-2679.wip.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
