[
https://issues.apache.org/jira/browse/TAJO-619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910229#comment-13910229
]
Hudson commented on TAJO-619:
-----------------------------
ABORTED: Integrated in Tajo-master-build #84 (See
[https://builds.apache.org/job/Tajo-master-build/84/])
TAJO-619: SELECT count(1) after joins on text keys causes wrong plans.
(hyunsik:
https://git-wip-us.apache.org/repos/asf/?p=incubator-tajo.git&a=commit&h=9cce80cfe585e8b93f86542e38ec5b07972d05d6)
*
tajo-core/tajo-core-backend/src/test/resources/results/TestCaseByCases/testTAJO619Case.result
*
tajo-core/tajo-core-backend/src/test/java/org/apache/tajo/engine/query/TestCaseByCases.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/engine/planner/ExprNormalizer.java
* CHANGES.txt
* tajo-algebra/src/main/java/org/apache/tajo/algebra/FunctionExpr.java
*
tajo-core/tajo-core-backend/src/test/resources/queries/TestCaseByCases/testTAJO619Case.sql
* tajo-algebra/src/main/java/org/apache/tajo/algebra/GeneralSetFunctionExpr.java
*
tajo-core/tajo-core-backend/src/main/java/org/apache/tajo/engine/planner/LogicalPlanner.java
*
tajo-core/tajo-core-backend/src/test/java/org/apache/tajo/LocalTajoTestingUtility.java
* tajo-algebra/src/main/java/org/apache/tajo/algebra/CountRowsFunctionExpr.java
* tajo-algebra/src/main/java/org/apache/tajo/algebra/OpType.java
> 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, 1.0-incubating
>
> Attachments: TAJO-619.patch
>
>
> {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)
