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

Don't hardcode KeyString version for clustered collections

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • Storage Execution
    • Execution Team 2021-11-29, Execution Team 2022-01-10

    Description

      Right now, the generated RecordId uses the default KeyString version

      The goal is to remove the hardcoded references to KeyString::Version::kLatestVersion and pip in the version provided upon the clustered collection creation.

      It would be nice for validate to also account for the version

       

      There is a mapping between the IndexVersion 'v' provided when creating a clusteredIndex and KeyString::Version

      IndexVersion :: KeyStringVersion
      1 :: 0

      2 :: 1

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            haley.connelly@mongodb.com Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: