Despite MongoDB having never used the extractor config, a case has come up in the wild where it's appeared in a config string, albeit with an empty value.
This happened because of an historical tool used for backups, which would explicitly set some configuration strings. It would set all strings that could have a persistent value, with an "empty string" fallback. As a result, some clusters that have been migrated from ancient Mongo versions have this key set with an empty value.
For this ticket, it's sufficient to check that the string is empty, otherwise fail with a reasonably obvious error message.
- is related to
-
WT-15209 Add a feature flag for eviction changes.
-
- Closed
-
-
WT-15246 Re-enable prepared testing that depends on new delta data format
-
- Blocked
-
-
WT-15230 Fix test_prepare_discover01
-
- Closed
-
-
WT-15267 Change python test test_prepare34 to trigger WT_UPDATE_MODIFY
-
- Closed
-
-
WT-15252 Skip test_layered32 on zSeries machines.
-
- Closed
-
- related to
-
WT-14989 Dump transaction information if timestamp validation failed in commit
-
- Closed
-
-
WT-15265 dist/ script to check metadata-persisted config removal
-
- Open
-