We got a request to allow upper layers to use existing code to manipulate configuration strings.
Idea: extend permissable encoding so that some JSON formatting is permitted: ignore curly braces at start/end, ignore quotes around names/values, allow colon instead of equals.
- is related to
-
WT-543 LSM core dump in the checkpoint code
- Closed
-
WT-581 test/format crash
- Closed
-
WT-682 wtperf failure: accessing a freed page
- Closed
-
WT-976 format checksum error
- Closed
-
WT-1017 voxer 10k - reconciliation illegally skipped an update
- Closed
-
WT-1245 Test format stress failure - strange LSM stack
- Closed
-
WT-1280 test/format eviction segfault in hazard_exclusive
- Closed
-
WT-1307 LSM read checksum panic
- Closed