Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | SERVER-39339 Remove `stdx/memory.h` | ADAM David Alan Martin | 2019-06-10 | 1 | -4/+4 |
| | |||||
* | SERVER-39338 Remove `stdx/functional.h` | ADAM David Alan Martin | 2019-06-10 | 1 | -2/+2 |
| | |||||
* | SERVER-39560 - remove leading blank line on all C++ files | Billy Donahue | 2019-02-13 | 1 | -1/+0 |
| | | | | | | Remove leading comments that are just stating the filename. Move any file-level comments below the copyright banner. Remove leading blank lines. | ||||
* | SERVER-38800 OpObserver accepts numRecords for drop and rename operations | Benety Goh | 2019-01-08 | 1 | -5/+9 |
| | |||||
* | SERVER-37443 Make catalog objects survive collection rename. | David Storch | 2018-10-23 | 1 | -3/+10 |
| | | | | | | This change only applies to collection renames within the same database. Rename across databases requires copying the data, and the resulting collection will have a new UUID. | ||||
* | SERVER-37651 Update header files with new license | Ramon Fernandez | 2018-10-22 | 1 | -8/+10 |
| | |||||
* | SERVER-34615 Make UUIDCatalog updates for renameCollection atomic | Maria van Keulen | 2018-06-06 | 1 | -10/+29 |
| | |||||
* | SERVER-34196 remove redundant dropTarget boolean argument from ↵ | Benety Goh | 2018-03-30 | 1 | -3/+2 |
| | | | | OpObserver::onRenameCollection | ||||
* | SERVER-32843 Allow multiple times in OpObservers | ADAM David Alan Martin | 2018-03-01 | 1 | -16/+30 |
| | | | | | | | | | | | | | | | | | The OpObserverRegistry was introduced as an abstraction to allow decoupling making data modifications from the side effects, which need to happen as a result of these modifications, such as op log writes, retryable writes, etc. Some of the OpObserver's methods currently return the OpTime which resulted from logging the operation to the replication oplog. In addition, in certain cases, the OpTime resulting from an earlier OpObserver might be needed by a later one, which is the case with retryable writes. In order to support these requirements, the OpObserver(s) chain should have access to some common per-operation structure, where runtime information could be persisted. | ||||
* | SERVER-29602 New OpObserverRegistry to allow multiple observers | Geert Bosch | 2017-12-21 | 1 | -0/+175 |
Also removes sharding specific interfaces for OpObserver. |