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

Move the database level profile setting from Database into CollectionCatalog

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.7.0, 4.4.2
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4
    • Sprint:
      Execution Team 2020-05-18

      Description

      We want to make the Database class stateless so that we do not need to version the Database class like the Collection class.

      The Database class' _profile setting should go into the CollectionCatalog.

      The initial idea is that CollectionCatalog will hold a new map of database name to profile level. Geert suggested only adding entries to the map if a non-default setting is set. We already do map lookups to fetch the Database instance, so doing a map lookup in CollectionCatalog instead of fetching the Database for the profile level shouldn't make a difference. It would be nice to do away with the map lookup every Collection read must do to fetch the profiling level, if some reasonable means can be thought up.

      No need to version the profile level, per the project design.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              dianna.hohensee Dianna Hohensee
              Reporter:
              dianna.hohensee Dianna Hohensee
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: