[
https://issues.apache.org/jira/browse/PHOENIX-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900735#comment-14900735
]
Hudson commented on PHOENIX-2274:
---------------------------------
SUCCESS: Integrated in Phoenix-master #900 (See
[https://builds.apache.org/job/Phoenix-master/900/])
PHOENIX-2274 Sort-merge join could not optimize out the sort on the right table
(maryannxue: rev 65d56bba6d8782ca0a76a30958daa059e3652f16)
* phoenix-core/src/main/java/org/apache/phoenix/compile/QueryCompiler.java
* phoenix-core/src/main/java/org/apache/phoenix/compile/OrderByCompiler.java
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/SubqueryUsingSortMergeJoinIT.java
* phoenix-core/src/it/java/org/apache/phoenix/end2end/SortMergeJoinIT.java
> Sort-merge join could not optimize out the sort on the right table
> ------------------------------------------------------------------
>
> Key: PHOENIX-2274
> URL: https://issues.apache.org/jira/browse/PHOENIX-2274
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 4.5.2
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Priority: Minor
> Attachments: PHOENIX-2274.patch
>
>
> {code}
> CREATE TABLE t (
> mypk VARCHAR(100) NOT NULL PRIMARY KEY,
> mycol VARCHAR(200));
> SELECT * FROM t t1 JOIN t t2 ON t1.mypk = t2.mypk;
> {code}
> would produce a plan like:
> {code}
> SORT-MERGE-JOIN (INNER) TABLES
> CLIENT PARALLEL 1-WAY FULL SCAN OVER T
> AND
> CLIENT PARALLEL 1-WAY FULL SCAN OVER T
> SERVER SORTED BY [MYPK]
> CLIENT MERGE SORT
> {code}
> , while it should have generated a plan like:
> {code}
> SORT-MERGE-JOIN (INNER) TABLES
> CLIENT PARALLEL 1-WAY FULL SCAN OVER T
> AND
> CLIENT PARALLEL 1-WAY FULL SCAN OVER T
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
