[SERVER-77349] Update Bucket::decompressed after inserting measurements into existing buckets Created: 22/May/23  Updated: 14/Aug/23  Resolved: 14/Aug/23

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

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

Issue Links:
Depends
depends on SERVER-77347 Modify makeTimeseriesDecompressAndUpd... Closed
is depended on by SERVER-77454 Allow makeTimeseriesInsertOp() to ret... Closed
is depended on by SERVER-78389 Always call makeTimeseriesDecompressA... Closed
Duplicate
duplicates SERVER-77347 Modify makeTimeseriesDecompressAndUpd... Closed
Assigned Teams:
Storage Execution
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
Participants:

 Description   

When this member on Bucket is set, we take the makeTimeseriesDecompressAndUpdateOp() code path that deals with writing to compressed buckets when we're inserting new measurements into that bucket. This essentially supports writing to already compressed buckets and we can reuse this for the initial crude implementation.

After committing the new measurements, and the bucket is not being closed, we'll need to make sure to update Bucket::decompressed with the new compressed bucket and post-image so that the bucket is ready for the next set of measurements.


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