Uploaded image for project: 'Drivers'
  1. Drivers
  2. DRIVERS-654

Implement Handling of Native UUID Types Specification

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FY20Q3
    • Component/s: None
    • Security Level: Public
    • Labels:
      None
    • Epic Name:
      Support standard UUID representation
    • # Replies:
      0
    • Last comment by Customer:
      false

      Description

      Epic Summary

      Summary

      The Java, C#, and Python drivers natively support platform types for UUID, all of which by default encode them to and decode them from BSON binary subtype 3. However, each encode the bytes in a different order from the others. To improve interoperability, BSON binary subtype 4 was introduced and defined the byte order according to RFC 4122, and a mechanism to configure each driver to encode UUIDs this way was added to each driver. The legacy representation remained as the default for each driver.

      This specification moves MongoDB drivers further towards the standard UUID representation by requiring an application relying on native UUID support to explicitly specify the representation it requires.

      Drivers that support native UUID types will additionally create helpers on their BsonBinary class that will aid in conversion to and from the platform native UUID type.

      Cast of Characters

      Lead : Jeff
      Author : Jeff
      POCs : Java, .Net

      Documentation

      Scope Document
      Spec Document

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              rathi.gnanasekaran Rathi Gnanasekaran
              Participants:
              Last commenter:
              Nuno Costa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 27 weeks, 2 days ago
                Date of 1st Reply: