| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It is the timestamp of the most recent DDL operation on the collection.
Has different semantics from minVisibleSnapshot and will eventually replace it.
|
| |
|
| |
|
|
|
|
| |
are catalog conflicts
|
|
|
|
|
|
| |
Remove leading comments that are just stating the filename.
Move any file-level comments below the copyright banner.
Remove leading blank lines.
|
| |
|
|
|
|
|
|
|
|
|
| |
Restarting the catalog throws away the "minVisibleSnapshot" info on all
collections. This is typically safe for rollback, the value is reinstantiated
when replication recovery rolls forward from the stable timestamp. However, it's
possible to read behind the stable timestamp. Currently only test commands can
do so, but the future may formally expose this case particularly for sharded
cluster snapshot reads.
|
|
|
|
| |
This reverts commit dc849ad01396b513e61ae389b3bce4b28f3404be.
|
|
|
|
|
|
|
|
|
| |
Restarting the catalog throws away the "minVisibleSnapshot" info on all
collections. This is typically safe for rollback, the value is reinstantiated
when replication recovery rolls forward from the stable timestamp. However, it's
possible to read behind the stable timestamp. Currently only test commands can
do so, but the future may formally expose this case particularly for sharded
cluster snapshot reads.
|
|
|