Hyunsik Choi created TAJO-914:
---------------------------------
Summary: join queries with constant values can cause schema
mismatch in logical plan
Key: TAJO-914
URL: https://issues.apache.org/jira/browse/TAJO-914
Project: Tajo
Issue Type: Bug
Components: planner/optimizer
Reporter: Hyunsik Choi
Assignee: Hyunsik Choi
Fix For: 0.9.0
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.
{noformat}
select l_orderkey, '##' as col1 from lineitem join orders on l_orderkey =
o_orderkey group by l_orderkey, col1
{noformat}
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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
