[COMPASS-7550] [Cleanup] Avoid storing preferences maxTimeMS in compass-aggregations state Created: 20/Dec/23  Updated: 31/Jan/24

Status: Open
Project: Compass
Component/s: Aggregation pipeline
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Anna Henningsen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split from COMPASS-7408 [Service Injection] Set up service pr... Closed
Assigned Teams:
Developer Tools
Epic Link: COMPASS-7021
Story Points: 2
Sprint: Iteration Utahraptor

 Description   

We shouldn’t need to separately keep track of the preferences maxTimeMS value in the redux slice in compass-aggregations. Instead, we should use React usePreference() for frontend components and the redux thunk argument for actions.


Generated at Wed Feb 07 22:46:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.