[
https://issues.apache.org/jira/browse/TAJO-914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071587#comment-14071587
]
Hudson commented on TAJO-914:
-----------------------------
SUCCESS: Integrated in Tajo-master-build #312 (See
[https://builds.apache.org/job/Tajo-master-build/312/])
TAJO-914: join queries with constant values can cause schema mismatch in
logical plan. (hyunsik: rev 326be451ded71099b88bdb6a50c40946df0af206)
* tajo-core/src/test/resources/queries/TestCaseByCases/testTAJO914Case4.sql
* tajo-core/src/test/java/org/apache/tajo/engine/query/TestCaseByCases.java
* tajo-core/src/test/resources/results/TestCaseByCases/testTAJO914Case2.result
* tajo-core/src/test/resources/results/TestCaseByCases/testTAJO914Case1.result
* tajo-core/src/test/resources/results/TestCaseByCases/testTAJO914Case4.result
* tajo-core/src/test/resources/results/TestCaseByCases/testTAJO914Case3.result
* tajo-core/src/main/java/org/apache/tajo/engine/utils/SchemaUtil.java
* CHANGES
* tajo-core/src/test/resources/queries/TestCaseByCases/testTAJO914Case3.sql
* tajo-core/src/test/resources/queries/TestCaseByCases/testTAJO914Case2.sql
* tajo-core/src/test/resources/queries/TestCaseByCases/testTAJO914Case1.sql
> 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)
