[PHOENIX-6507] DistinctAggregatingResultIterator should keep original tuple order of the AggregatingResultIterator

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 4.16.1, 5.1.2
• Fix Version/s: 4.17.0, 5.2.0, 5.1.3
• Assignee: chenglei
• Reporter: chenglei
• Created: 07/Jul/21 08:29
• Updated: 16/Dec/22 10:15
• Resolved: 16/Jul/21 02:27

Description

Given following tables :

   create table test ( 
      pk1 varchar not null , 
      pk2 varchar not null, 
      pk3 varchar not null,
       v1 varchar, 
       v2 varchar, 
      CONSTRAINT TEST_PK PRIMARY KEY ( pk1,pk2,pk3))

The result of the following sql may be incorrect:

   select distinct pk1,max(v1) from test group by pk1,pk2,pk3 order by pk1

The problem is the order by is complied out because it is the prefix of the group by, but for distinct, DistinctAggregatingResultIterator using HashSet to rearrange the aggregated tuples.

Issue Links

• links to: GitHub Pull Request #1262