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

Remove the readonly option from WT_SESSION::create and WT_SESSION::alter

    • 5
    • Storage - Ra 2022-05-16, Storage - Ra 2022-05-30


      WT_SESSION::create() lets you create a new table with readonly=true. This is documented as a legal option to create(). The library lets you insert to the resulting table, but panics at connection close when it can't checkpoint or evict the dirty pages from that table.

      If creating a readonly table supports a desired use case, then WT should handle it without failing, probably by returning an error when performing updates on a cursor on the table. 

      Alternately, if there is not use case for this create option, we should detect it and return an error in the create() call.

      We decided that this option is no longer needed in WT_SESSION::create and WT_SESSION::alter.

      Acceptance Criteria (Definition of Done)

      1. Remove readonly option from WT_SESSION::create and WT_SESSION::alter
      2. Remove the option and all no longer relevant test cases from all the test frameworks

            monica.ng@mongodb.com Monica Ng
            keith.smith@mongodb.com Keith Smith
            0 Vote for this issue
            5 Start watching this issue