Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-49916

use storageSize instead of size when creating capped collections

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: 3.6.17, 4.0.19, 4.2.8
    • Component/s: Storage
    • Labels:
    • Execution Team 2020-08-24, Execution Team 2020-09-07, Execution Team 2020-09-21

      When creating capped collections you have to define its maximal size in bytes which is size of uncompressed data.
      However, since wiredTiger stores data compressed on disk, it is very difficult to guess the right "size" not to exceed a certain amount of data on disk because the compression factor (and thus the "storageSize") may vary.

      Therefore, it would be much better to be able to define the maximal "storageSize" when creating a capped collection. For downwards compatibility, the "size" parameter can co-exists.

      This feature is even more important as long as capped collections cannot be resized.

            michael.gargiulo@mongodb.com Michael Gargiulo
            kay.agahd@idealo.de Kay Agahd
            1 Vote for this issue
            10 Start watching this issue