[SERVER-44139] Allow collection creation inside a multi-doc txn for a single-node replica set Created: 21/Oct/19  Updated: 29/Oct/23  Resolved: 07/Jan/20

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

Type: New Feature Priority: Minor - P4
Reporter: Geert Bosch Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-44138 Stash UncommittedCollections resource... Closed
Related
related to SERVER-45368 Allow collection and index creation i... Closed
related to SERVER-45371 Remove opCtx as argument to KVEngine:... Closed
related to SERVER-57928 create_collection.js should use a de... Closed
is related to SERVER-46009 CommandHelpers::canUseTransactions() ... Closed
is related to SERVER-44852 Have secondary oplog application hand... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2019-12-16, Execution Team 2020-01-13, Execution Team 2019-12-30
Participants:
Linked BF Score: 33

 Description   

Implement the most basic multi-doc collection creation. The following should work in a txn for a single node replica set:

  • create a collection
  • insert a document in that collection
  • find and return the document
  • commit/abort the transaction

This feature should be gated on FCV 4.4.



 Comments   
Comment by Githook User [ 07/Jan/20 ]

Author:

{'name': 'Maria van Keulen', 'email': 'maria.vankeulen@mongodb.com', 'username': 'mvankeulen94'}

Message: SERVER-44139 Allow collection creation in multi-document transactions

This commit allows the feature for single-node replica sets only.
Branch: master
https://github.com/mongodb/mongo/commit/cb293d4de806e8089e4fb08926124ed18b2fa578

Comment by Maria van Keulen [ 20/Dec/19 ]

SERVER-44852 will handle replication of transactions with commands, so this ticket will only implement the feature for a single-node replica set.

Comment by Daniel Gottlieb (Inactive) [ 19/Nov/19 ]

geert.bosch and I expect this ticket will need to skip generating an opTime for createCollection when inside of a multi-stmt transaction here. Which will likely result in some sort of refactor to thread the minimumVisibleTimestamp into the uncommitted collection prior to registering it in the catalog.

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