jay wong created PHOENIX-84:
-------------------------------
Summary: explain the query plan is not the actually order
Key: PHOENIX-84
URL: https://issues.apache.org/jira/browse/PHOENIX-84
Project: Phoenix
Issue Type: Bug
Affects Versions: 3.0.0
Reporter: jay wong
Fix For: 3.0.0
explain select test_join1.varchar_pk,sum(test_join2.int_column),
min(test_join2.int_column_b) from test_join1 left join test_join2 on
test_join1.int_column = test_join2.int_column where test_join1.int_column > 0
GROUP BY TEST_JOIN1.VARCHAR_PK;
+------------+
| PLAN |
+------------+
| CLIENT PARALLEL 32-WAY FULL SCAN OVER TEST_JOIN1 |
| SERVER FILTER BY INT_COLUMN > 0 |
| SERVER AGGREGATE INTO ORDERED DISTINCT ROWS BY [TEST_JOIN1.VARCHAR_PK] |
| CLIENT MERGE SORT |
| PARALLEL EQUI-JOIN 1 HASH TABLES: |
| BUILD HASH TABLE 0 |
| CLIENT PARALLEL 32-WAY FULL SCAN OVER TEST_JOIN2 |
but in my observe
first step : full scan test_join2 with filter and send the result.
sencod step: full scan test_join1 with equi-join.
and didn't find client merge sort.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
