[ https://issues.apache.org/jira/browse/PHOENIX-4508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16315174#comment-16315174 ]
Hadoop QA commented on PHOENIX-4508: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12904968/PHOENIX-4508.patch against master branch at commit 2136b002c37db478ffea11233f9ebb80276d2594. ATTACHMENT ID: 12904968 {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:red}-1 release audit{color}. The applied patch generated 1 release audit warnings (more than the master's current 0 warnings). {color:green}+1 lineLengths{color}. The patch does not introduce lines longer than 100 {color:green}+1 core tests{color}. The patch passed unit tests in . Test results: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1704//testReport/ Release audit warnings: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1704//artifact/patchprocess/patchReleaseAuditWarnings.txt Console output: https://builds.apache.org/job/PreCommit-PHOENIX-Build/1704//console This message is automatically generated. > Wrong query plan generation > --------------------------- > > Key: PHOENIX-4508 > URL: https://issues.apache.org/jira/browse/PHOENIX-4508 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.13.2 > Reporter: Flavio Pompermaier > Assignee: Maryann Xue > Labels: planner, query > Attachments: PHOENIX-4508.patch > > > In my Phoenix tables I found that one query ens successfully while another > one, logically equal, does not (unless that I don't apply some tuning to > timeouts). > The 2 queries extract the same data but, while the first query terminates the > second does not. > PS: without the USE_SORT_MERGE_JOIN both queries weren't working > ---- > h2. First query > {code:sql} > SELECT /*+ USE_SORT_MERGE_JOIN */ COUNT(*) > FROM PEOPLE ds JOIN MYTABLE l ON ds.PERSON_ID = l.LOCALID > WHERE l.EID IS NULL AND l.DSID = 'PEOPLE' AND l.HAS_CANDIDATES = FALSE; > {code} > +---------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ > | PLAN > | EST_BYTES_READ | EST_ROWS_READ | > EST_INFO_TS | > +---------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ > | SORT-MERGE-JOIN (INNER) TABLES > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT 42-CHUNK 6168903 ROWS 11324622221 BYTES PARALLEL 3-WAY FULL SCAN > OVER PEOPLE | 14155777900 | 12077867 | > 1513754378759 | > | SERVER FILTER BY FIRST KEY ONLY > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT MERGE SORT > | 14155777900 | 12077867 | > 1513754378759 | > | AND (SKIP MERGE) > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT 15-CHUNK 5908964 ROWS 2831155679 BYTES PARALLEL 15-WAY RANGE > SCAN OVER MYTABLE [0] - [2] | 14155777900 | 12077867 | > 1513754378759 | > | SERVER FILTER BY (EID IS NULL AND DSID = 'PEOPLE' AND > HAS_CANDIDATES = false) | 14155777900 | 12077867 > | 1513754378759 | > | SERVER SORTED BY [L.LOCALID] > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT MERGE SORT > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT AGGREGATE INTO SINGLE ROW > | 14155777900 | 12077867 | > 1513754378759 | > +---------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ > 10 rows selected (0.041 seconds) > ---- > h2. Second query > {code:sql} > SELECT /*+ USE_SORT_MERGE_JOIN */ COUNT(*) > FROM (SELECT LOCALID FROM MYTABLE > WHERE EID IS NULL AND DSID = 'PEOPLE' AND HAS_CANDIDATES = FALSE) l JOIN > PEOPLE ds ON ds.PERSON_ID = l.LOCALID; > {code} > +--------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ > | PLAN > | EST_BYTES_READ | EST_ROWS_READ | > EST_INFO_TS | > +--------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ > | SORT-MERGE-JOIN (INNER) TABLES > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT 15-CHUNK 5908964 ROWS 2831155679 BYTES PARALLEL 3-WAY RANGE SCAN > OVER MYTABLE [0] - [2] | 14155777900 | 12077867 | 1513754378759 | > | SERVER FILTER BY (EID IS NULL AND DSID = 'PEOPLE' AND > HAS_CANDIDATES = false) | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT MERGE SORT > | 14155777900 | 12077867 | > 1513754378759 | > | AND (SKIP MERGE) > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT 42-CHUNK 6168903 ROWS 11324622221 BYTES PARALLEL 42-WAY FULL > SCAN OVER PEOPLE | 14155777900 | 12077867 | > 1513754378759 | > | SERVER FILTER BY FIRST KEY ONLY > | 14155777900 | 12077867 | > 1513754378759 | > | SERVER SORTED BY [DS.PERSON_ID] > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT MERGE SORT > | 14155777900 | 12077867 | > 1513754378759 | > | CLIENT AGGREGATE INTO SINGLE ROW > | 14155777900 | 12077867 | > 1513754378759 | > +--------------------------------------------------------------------------------------------------------------+-----------------+----------------+----------------+ -- This message was sent by Atlassian JIRA (v6.4.14#64029)