[ https://issues.apache.org/jira/browse/PHOENIX-3452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662633#comment-15662633 ]
chenglei edited comment on PHOENIX-3452 at 11/14/16 3:29 AM: ------------------------------------------------------------- [~jamestaylor],I uploaded a new patch: PHOENIX-3452_v3.patch, enhanced unit tests and IT tests,these test cases will be ok after the PHOENIX-3469 is applied,and I will uploaed a new patch after the PHOENIX-3469 is applied. [~jamestaylor],just have a look,thanks. By the way,in my unit tests and IT tests,I only test "group by ORGANIZATION_ID, CONTAINER_ID", not "group by CONTAINER_ID,ORGANIZATION_ID", because I found PHOENIX-3451 interfering with "group by CONTAINER_ID,ORGANIZATION_ID" test cases. I will add these cases in PHOENIX-3451 patch. I think the order of fixing these three bugs is: 1.PHOENIX-3469. 2.PHOENIX-3452 3.PHOENIX-3451,which is a very serious and important bug. was (Author: comnetwork): [~jamestaylor],I uploaded a new patch: PHOENIX-3452_v3.patch, enhanced unit tests and IT tests,these test cases will be ok after the PHOENIX-3469 is applied,and I will uploaed a new patch after the PHOENIX-3469 is applied. [~jamestaylor],just have a look,thanks. By the way,in my unit tests and IT tests,I only test "group by ORGANIZATION_ID, CONTAINER_ID", not "group by CONTAINER_ID,ORGANIZATION_ID", because I found PHOENIX-3451 interfere with "group by CONTAINER_ID,ORGANIZATION_ID" test cases. I will add these cases in PHOENIX-3451 patch. I think the order of fixing these three bugs is: 1.PHOENIX-3469. 2.PHOENIX-3452 3.PHOENIX-3451,which is a very serious and important bug. > Secondary index and query using distinct: ORDER BY doesn't work correctly > ------------------------------------------------------------------------- > > Key: PHOENIX-3452 > URL: https://issues.apache.org/jira/browse/PHOENIX-3452 > Project: Phoenix > Issue Type: Bug > Affects Versions: 4.8.0 > Reporter: Joel Palmert > Assignee: chenglei > Attachments: PHOENIX-3452_v2.patch, PHOENIX-3452_v3.patch > > > This may be related to PHOENIX-3451 but the behavior is different so filing > it separately. > Steps to repro: > CREATE TABLE IF NOT EXISTS TEST.TEST ( > ORGANIZATION_ID CHAR(15) NOT NULL, > CONTAINER_ID CHAR(15) NOT NULL, > ENTITY_ID CHAR(15) NOT NULL, > SCORE DOUBLE, > CONSTRAINT TEST_PK PRIMARY KEY ( > ORGANIZATION_ID, > CONTAINER_ID, > ENTITY_ID > ) > ) VERSIONS=1, MULTI_TENANT=TRUE, REPLICATION_SCOPE=1, TTL=31536000; > CREATE INDEX IF NOT EXISTS TEST_SCORE ON TEST.TEST (CONTAINER_ID, SCORE DESC, > ENTITY_ID DESC); > UPSERT INTO test.test VALUES ('org1','container1','entityId6',1.1); > UPSERT INTO test.test VALUES ('org1','container1','entityId5',1.2); > UPSERT INTO test.test VALUES ('org1','container1','entityId4',1.3); > UPSERT INTO test.test VALUES ('org1','container1','entityId3',1.4); > UPSERT INTO test.test VALUES ('org1','container1','entityId2',1.5); > UPSERT INTO test.test VALUES ('org1','container1','entityId1',1.6); > SELECT DISTINCT entity_id, score > FROM test.test > WHERE organization_id = 'org1' > AND container_id = 'container1' > ORDER BY score DESC > Notice that the returned results are not returned in descending score order. > Instead they are returned in descending entity_id order. If I remove the > DISTINCT or remove the secondary index the result is correct. -- This message was sent by Atlassian JIRA (v6.3.4#6332)