[SERVER-56946] Clean up the hardcoded bucketMaxSpanSeconds values in query code. Created: 14/May/21  Updated: 29/Oct/23  Resolved: 08/Sep/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.2.0-rc0

Type: Task Priority: Major - P3
Reporter: Ethan Zhang (Inactive) Assignee: Ivan Fefer
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Gantt Dependency
has to be done after SERVER-56124 Provide an alias to $_internalUnpackB... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-05-31, Query Execution 2021-06-14, Query Execution 2021-06-28, Query Execution 2021-07-12, QE 2022-09-19
Participants:

 Description   

In document_source_internal_unpack_bucket and some other query code, we have hardcoded values 3600 for bucketMaxSpanSeconds. We should clean them up



 Comments   
Comment by Githook User [ 08/Sep/22 ]

Author:

{'name': 'Ivan Fefer', 'email': 'ivan.fefer@mongodb.com', 'username': 'Fefer-Ivan'}

Message: SERVER-56946 Use timeseries::getMaxSpanSecondsFromGranularity instead of hard-coded constant
Branch: master
https://github.com/mongodb/mongo/commit/b9955a03d89b369beb577e29cfc0478674264802

Comment by David Storch [ 14/May/21 ]

Flagging for scheduling, since I think this belongs in a sprint.

Generated at Thu Feb 08 05:40:35 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.