[SERVER-57504] Minimize the number of damages created for an internal time-series bucket collection update Created: 07/Jun/21  Updated: 29/Oct/23  Resolved: 17/Jun/21

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

Type: Task Priority: Major - P3
Reporter: Yuhong Zhang Assignee: Yuhong Zhang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-56520 Time-series inserts spent a lot of ti... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-06-14, Execution Team 2021-06-28
Participants:

 Description   

The damage vector for a time-series bucket collection update should have the size of the number of top level fields plus one (when updating both min and max) or two (when updating only max).

The code is blocked to integrate with the time-series update code path due to performance issues found in wiredtiger, but we would like to keep the logic in the codebase for future use.



 Comments   
Comment by Vivian Ge (Inactive) [ 06/Oct/21 ]

Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you!

Comment by Githook User [ 17/Jun/21 ]

Author:

{'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}

Message: SERVER-57504 Minimize the number of damages created for an internal time-series bucket collection update
Branch: master
https://github.com/mongodb/mongo/commit/04289ff03fb8c70969266e78e53940a8bcb2cb13

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