[TAJO-543] InsertNode and CreateTableNode should play their roles

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.8.0
• Component/s: Planner/Optimizer
• Assignee: Hyunsik Choi
• Reporter: Hyunsik Choi
• Created: 22/Jan/14 03:26
• Updated: 22/Jan/14 08:55
• Resolved: 22/Jan/14 08:51

Description

Currently, CreateTableNode and InsertNode are just intermediate representations. They are rewritten to StoreTableNode. But, StoreTableNode does not contain some necessary fields, such as output table, target table, target columns, overwrite flag and create table flag. So far, these fields are kept in QueryContext.

This implementation causes unnecessary and complex rewrite of DistributedQueryHookManager. As a result, it is hard to maintain and manage CREATE/INSERT plans.

The main objective of this issue is to improve LogicalPlanner to use CreateTableNode and InsertNode throughout the planning phase and eliminate complex rewrite in DistributedQueryHookManager.

Issue Links

• relates to: TAJO-475 Table partition catalog recap