| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
inherit collection level collation
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This corrects previously incorrect behavior where tailable cursors on unreplicated capped
collections like the profile collection could miss writes
This pushes non-oplog capped collection visibility logic outside of the storage engine layer
|
| |
|
|
|
|
| |
in each shard
|
| |
|
| |
|
|
|
|
| |
served by CSI
|
| |
|
|
|
|
|
|
| |
cannot be served by CSI"
This reverts commit 8583f66c0126e3d5ddf25c62a242b01c3d82bc19.
|
|
|
|
| |
served by CSI
|
|
|
|
| |
an _id column cursor (also dense) is present
|
| |
|
|
|
|
| |
with tenantId
|
|
|
|
| |
chunk operations
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This allows readers to use Collections fully in sync with the multi-document transaction snapshot and eliminates the need for the pessimistic "catalog conflicting timestamp".
Write operations checks that they are operating on the latest version of the collection and throw WCE if not.
|
| |
|
|
|
|
| |
bucket atomically
|
| |
|
| |
|
|
|
|
| |
on time"
|
| |
|
| |
|
|
|
|
| |
sharded clusters
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
bucketMaxSpanSeconds in create and collMod commands
|
| |
|
| |
|