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

session->alter doesn't mark the altered table dirty

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Checkpoints
    • Storage Engines
    • 3
    • StorEng - 2024-11-12, StorEng - 2024-11-26
    • v8.0

      During checkpoint, WiredTiger writes out the checkpoint information into the table itself so that the table can be used alone as the input for session->create(..."import=(enabled,repair=true)") and the metadata for the create can be found in the file itself.

      When a table's configuration setting is changed via session->alter, the metadata is updated, but the table itself is not marked dirty. This means that on the next checkpoint, the latest checkpoint information stored in the table itself will not reflect the successful alteration. If that table is then used for an import=(enabled,repair=true) then the newly imported table cannot find the correct altered configuration setting.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            sue.loverso@mongodb.com Susan LoVerso
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: