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

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: