Hyunsik Choi created TAJO-619:
---------------------------------
Summary: SELECT count(1) after joins on text keys causes wrong
plans
Key: TAJO-619
URL: https://issues.apache.org/jira/browse/TAJO-619
Project: Tajo
Issue Type: Bug
Components: planner/optimizer
Reporter: Hyunsik Choi
Assignee: Hyunsik Choi
Priority: Minor
Fix For: 0.8-incubating
{code}
select count(1) from table1 join table2 on table1.name = table2.name;
{code}
When there are constant values in select list and equi-join keys are text
columns, it causes some errors due to schema mismatch.
Its cause of this bug is as follows:
* the number 1 results in a generated column name '?literal'.
* This name is used in both table1 and table2. Output schemas of table1 and
table2 include ?literal
* The input schema of join has only three columns because ?literal is
duplicated name.
So, its essential bug may be one of following:
* The constant value is evaluated twice. In other words, literal? occurs in
both table1 and table2.
* Schema class does not allow the same column name.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
