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

Extend test_tiered07.py to test all WT_SESSION::drop options

    • Type: Icon: New Feature New Feature
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • 3
    • Storage - Ra 2022-04-04

      Summary

      When dropping tiered tables, we only want to drop the local content. The dropping of the shared objects will happen during garbage collection. That means that a drop will remove the local writable object and all metadata referencing the table including the metadata for objects that will still exist on the shared storage.

      The work for implementing drop was completed in WT-7375. There is a basic test for drop in test_tiered07.py. That test should be expanded to include testing all possible configurations for drop and making sure tiered storage does the right thing for each one.

      Acceptance Criteria (Definition of Done)
      We need to test both options "force" and "remove_files". We need to make sure that metadata entries are removed and the corresponding files are deleted, or not deleted if remove_files=false.

      Shared files must not be deleted. There should be a test for that too. 

            Assignee:
            monica.ng@mongodb.com Monica Ng
            Reporter:
            alexey.anisimov@mongodb.com Alexey Anisimov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: