[TAJO-914] join queries with constant values can cause schema mismatch in logical plan

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.9.0
• Component/s: Planner/Optimizer
• Assignee: Hyunsik Choi
• Reporter: Hyunsik Choi
• Created: 07/Jul/14 06:59
• Updated: 23/Jul/14 10:43
• Resolved: 23/Jul/14 09:28

Description

The following query can cause a schema mismatch problem between join node and its both child scan nodes. The main cause that '##' col1 are evaluated in both ScanNode. Because a schema cannot include the same column names, one col1 is omitted. So, it causes the schema mismatch problem.

select l_orderkey, '##' as col1 from lineitem join orders on l_orderkey = o_orderkey group by l_orderkey, col1

This is a critical bug. So, I've uploaded the urgent workaround bug fix. Later, I'll fix it in more valid and stable manner. I already created the Jira issue (TAJO-895) for that way.

Issue Links

• relates to: TAJO-895 ConstEval should not be included in target list of projectable nodes