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

Break up CollectionOptions into one struct for accepting user options and another for persisting to the catalog

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution

    Description

      The CollectionOptions struct is a mixture of some user-provided options that are serialized and persisted directly to the durable catalog (i.e. capped) and others that are user-provided but and dispatched into other actions (i.e. timeseries), but never directly serialized.

      This multipurpose struct accepts a ParseKind flag that validates options based on whether the struct is being used for storage or user options.

      It would make sense to have one structure for holding all user-provided options and another that is used only to serialize/deserialize to the catalog.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            louis.williams@mongodb.com Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: