Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Unresolved
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Assigned Teams:

Storage Execution
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

This is effectively reopening ~~SERVER-52965~~ now that ~~SERVER-16049~~ is complete and undoing ~~SERVER-47824~~ and ~~SERVER-47574~~. We could certainly add these two features separately. As we want to use snapshot reads and transactions internally to support other features, having capped collections be less "special" will make this easier.

is related to

SERVER-47824 Ban transaction snapshot reads on capped collections

Closed

SERVER-16049 Replicate capped collection deletes explicitly

Closed

SERVER-53965 Add option to use transactions with capped collections

Closed

SERVER-47574 Ban non-transaction snapshot reads on capped collections

Closed

related to

SERVER-88230 Prevent resharding for unsharded capped collection from stashing collection

Closed

SERVER-86290 Allow snapshot reads on capped collections

Closed

(1 related to)

Assignee:: [DO NOT USE] Backlog - Storage Execution Team
Reporter:: Judah Schvimer
Participants:: [DO NOT USE] Backlog - Storage Execution Team, Judah Schvimer, Louis Williams, Wenbin Zhu
Votes:: 0 Vote for this issue
Watchers:: 15 Start watching this issue

Created:: Feb 18 2022 12:41:02 AM UTC
Updated:: Mar 19 2024 07:08:40 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates