[SERVER-80562] Timeseries group rewrite blocks count rewrite when collation doesn't match Created: 30/Aug/23  Updated: 02/Feb/24

Status: In Code Review
Project: Core Server
Component/s: None
Affects Version/s: 7.1.0-rc0
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Gil Alon Assignee: Arun Banala
Resolution: Unresolved Votes: 0
Labels: bkp
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Problem/Incident
is caused by SERVER-78235 pushdown $group ahead of unpack with ... Closed
Assigned Teams:
Query Integration
Backport Requested:
v7.3
Sprint: QI 2023-09-18, QI 2023-10-02, QI 2023-10-16, QI 2023-10-30, QI 2023-11-13, QI 2023-11-27, QI 2023-12-11, QI 2023-12-25, QI 2024-01-08, QI 2024-01-22, QI 2024-02-05, QI 2024-02-19
Participants:

 Description   

In SERVER-78235 we added a rewrite for $count accumulator in a $group stage. However, we need to move the check if the collation matches to rewriteMinMaxGroupAccm(), since $count doesn't depend on the collation. This way even if the collation doesn't match we can rewrite a $group stage that has a $count accumulator.


Generated at Thu Feb 08 06:43:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.