[
https://issues.apache.org/jira/browse/TAJO-475?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13882530#comment-13882530
]
Hyunsik Choi commented on TAJO-475:
-----------------------------------
The updated patch additionally does as follows:
* Add getLogicalSchema and getPhysicalSchema to ScanNode
** getLogicalSchema provides a schema including partition columns, and it is
used for logical planning
** getPhysicalSchema just provides a schema for stored columns, and it will be
used for actual scanners
* Add logical schema to TableDesc
* Add TableSchema to RelationNode
* Improve SeqScanNode and rewrite method to use logical schema
* Simplify and cleanup the succeeded event in Query
The main objective of this additional work is to separate the schema of
ScanNode into more clear definitions. So far, we ambiguously use an output
schema as a table schema of ScanNode in many cases. It have made us much
confuse. This work fixes this problem.
For example, consider a following schema with partition description:
{code}
create table tb1 (col1 int4, col2 int4) partition by column(key float8)
{code}
Its logical schema will be (col1 int4, col2 int4, key float8), whereas its
physical schema will be (col1 int4, col2 int4). The output schema of ScanNode
is just determined by a target list of ScanNode.
> Table partition catalog recap
> -----------------------------
>
> Key: TAJO-475
> URL: https://issues.apache.org/jira/browse/TAJO-475
> Project: Tajo
> Issue Type: Sub-task
> Components: catalog
> Reporter: Min Zhou
> Assignee: Min Zhou
> Fix For: 0.8-incubating
>
> Attachments: TAJO-475_140127_112723.patch, TAJO-475_2.patch,
> tajo-475-v2.patch, tajo-475-v3.patch, tajo-475-v4.patch, tajo-475.diff
>
>
> Query master need to know where partitions of memory cached table locate.
> At least we need a meta table contain such information
> |partition_id|
> |partition_value|
> |ordinal_position|
> |locations|
> Any suggestion?
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
