-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
At the moment schema operations that involve complex tables can result in multiple updates to the metadata that aren't wrapped in a single transaction - which means that such operations aren't atomic.
We should use a transaction so those changes are grouped into a single unit of work.
We attempted to make this change in WT-3829, but that resulted in some unexpected failures for MongoDB. The broken code was disabled as part of WT-3964, we should understand those failures, and make a correct version of that change.
- depends on
-
WT-3964 Stop wrapping schema operations in a transaction
- Closed
- is related to
-
WT-3829 WiredTiger metadata can be logically inconsistent.
- Closed
-
WT-3963 Add a schema intensive abort testing
- Closed
- related to
-
WT-11952 Testy failed with "cannot be used until all column groups are created" while calling verify
- Open