Don't hardcode KeyString version for clustered collections

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Execution Team 2021-11-29, Execution Team 2022-01-10
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            Haley Connelly
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: