[SERVER-53958] Handle time-series inserts with different write concerns Created: 21/Jan/21  Updated: 29/Oct/23  Resolved: 02/Feb/21

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

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

Issue Links:
Depends
Problem/Incident
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-02-08
Participants:
Linked BF Score: 50

 Description   

We should add test coverage for inserting into a time-series collection with different write concerns, and make any changes/fixes as needed. We may need to start new buckets based on the write concern.



 Comments   
Comment by Githook User [ 02/Feb/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-53958 Tag timeseries_write_concern.js with requires_replication
Branch: master
https://github.com/mongodb/mongo/commit/ae0a72e4798a73d55addf4259f4bf1a7edafa9ae

Comment by Githook User [ 29/Jan/21 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-53958 Test time-series inserts with different write concerns in the same bucket
Branch: master
https://github.com/mongodb/mongo/commit/bf71cf09aa021bef2f5e3aeacffdb92a286738ff

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