[SERVER-85100] POC design for time-series updates and deletes Created: 09/Dec/22  Updated: 12/Jan/24  Resolved: 19/Jan/23

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

Type: Task Priority: Major - P3
Reporter: Charlie Swanson Assignee: Charlie Swanson
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-72517 Tests for former featureFlagTimeserie... Closed
is related to SERVER-72109 [POC] Bucket catalog support for time... Closed
Sprint: Execution Team 2022-12-26, Execution Team 2023-01-09, Execution Team 2023-01-23
Participants:

 Comments   
Comment by Charlie Swanson [ 19/Jan/23 ]

I'm going to call this one "Done" - skipping some of the refactoring and more tests for future tickets which I'll file shortly!

Comment by Charlie Swanson [ 04/Jan/23 ]

I'm using the poc-timeseries-deletes branch to track the work. Starting with multi-deletes. Here's the diff view, I think I have a decent start: https://github.com/10gen/mongo/compare/charlie.swanson/poc-timeseries-deletes?expand=1

Going to look into the following still:

  • More testing - look for or add collation tests
  • Refactoring - this approach adds a bad API to ParsedDelete to reset the CanonicalQuery. It'd be better if we could figure out the correct CanonicalQuery right from the start.
  • Properly tracking stats like nDeleted
  • explain?

I think I need to wait on https://jira.mongodb.org/browse/SERVER-72109 before I can work on and test some of the retry logic for WriteConflicts. That should be pretty interesting to do too.

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