Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-4204

Add test case to verify complex metadata

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None

      During a recent discussion about reproducing a fsyncLock/snapshotting backup issue, below suggestions were made by michael.cahill and sue.loverso:

      Right now for WiredTiger.backup there's assumption that we can fprintf the keys and values, and that they won’t contain embedded newlines (i.e., we can read back the key and value in a single line). Particularly with app_metadata, which MongoDB uses, and which is complicated for indexes, this assumption is questionable.

      It would be helpful to add a test case to test_alter03.py such as test_alter03_complex_metadata. The test should set up a table, and then set up a complex JSON metadata string, then alter the app_metadata with that JSON and verify it. An example of complex JSON strings can be found in test_jsondump02.py. Perhaps the code in there using bin_unicode and mixed_unicode can be used to test embedded special characters in the app_metadata.

            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            luke.chen@mongodb.com Luke Chen
            0 Vote for this issue
            2 Start watching this issue