[
https://issues.apache.org/jira/browse/PHOENIX-2679?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15549497#comment-15549497
]
Maryann Xue commented on PHOENIX-2679:
--------------------------------------
The reason why we need to put them in the Schema (at a later stage though) is
that we need to get RelOptTable to create a new TableScan.
{code}
List<String> name = new ArrayList<String>(table.getQualifiedName());
name.set(name.size() - 1,
table.unwrap(PhoenixTable.class).getFlattenedName());
RelOptTable flattenedTable =
table.getRelOptSchema().getTableForMember(name);
PhoenixTableScan newScan = PhoenixTableScan.create(scan.getCluster(),
flattenedTable);
{code}
So these shadow tables are just Objects and do not have much impact other than
that.
> 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)
