[SERVER-77347] Modify makeTimeseriesDecompressAndUpdateOp() to return a compressed update entry Created: 22/May/23  Updated: 29/Oct/23  Resolved: 24/Aug/23

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

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

Issue Links:
Depends
is depended on by SERVER-77349 Update Bucket::decompressed after ins... Closed
is depended on by SERVER-78389 Always call makeTimeseriesDecompressA... Closed
Duplicate
is duplicated by SERVER-77349 Update Bucket::decompressed after ins... Closed
is duplicated by SERVER-78389 Always call makeTimeseriesDecompressA... Closed
Problem/Incident
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Sprint: Execution NAMR Team 2023-06-26, Execution NAMR Team 2023-07-24, Execution NAMR Team 2023-08-07, Execution NAMR Team 2023-08-21, Execution NAMR Team 2023-09-04
Participants:
Linked BF Score: 12

 Description   

This code path is currently unused since re-opening compressed buckets is disabled when the feature flag is disabled. It takes in a compressed bucket and changes that need to be applied to the bucket. It returns the transform-style update in an uncompressed state that gets applied to the bucket collection.

We can repurpose this function and have it return the transform-style update in a compressed state by compressing the post-image. We'll also have to sort the bucket on time before returning the compressed update entry, which is a property of compressed buckets today.



 Comments   
Comment by Githook User [ 24/Aug/23 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-77347 Updates to time-series buckets are always compressed
Branch: master
https://github.com/mongodb/mongo/commit/4a1a942805160bc730732ac9f9ea23b40ea97571

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