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

Drivers Support for indexing and querying on UUID and null datatype

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Component/s: Index Management
    • None
    • Builder Changes Needed
    • Hide

      Summary of necessary driver changes

      • Expecting that no changes are required, but teams with builder support should confirm they support querying for null values and formatted UUIDs. If changes are not required in a particular driver, close as Works as Designed

      Commits for syncing spec/prose tests
      (and/or refer to an existing language POC if needed)

      • N/A

      Context for other referenced/linked tickets

      • Users must be able to query for
        • UUID types using the equals and in operator
        • null using the equals operator
      Show
      Summary of necessary driver changes Expecting that no changes are required, but teams with builder support should confirm they support querying for null values and formatted UUIDs. If changes are not required in a particular driver, close as Works as Designed Commits for syncing spec/prose tests (and/or refer to an existing language POC if needed) N/A Context for other referenced/linked tickets Users must be able to query for UUID types using the equals and in operator null using the equals operator
    • $i18n.getText("admin.common.words.hide")
      Key Status/Resolution FixVersion
      CSHARP-4938 Fixed 3.1.0
      JAVA-5299 Blocked
      PHPORM-135 Works as Designed doctrine-2.6.0
      $i18n.getText("admin.common.words.show")
      #scriptField, #scriptField *{ border: 1px solid black; } #scriptField{ border-collapse: collapse; } #scriptField td { text-align: center; /* Center-align text in table cells */ } #scriptField td.key { text-align: left; /* Left-align text in the Key column */ } #scriptField a { text-decoration: none; /* Remove underlines from links */ border: none; /* Remove border from links */ } /* Add green background color to cells with FixVersion */ #scriptField td.hasFixVersion { background-color: #00FF00; /* Green color code */ } /* Center-align the first row headers */ #scriptField th { text-align: center; } Key Status/Resolution FixVersion CSHARP-4938 Fixed 3.1.0 JAVA-5299 Blocked PHPORM-135 Works as Designed doctrine-2.6.0

      Summary

      Users can now natively query UUID and null fields within Atlas Search. This functionality will be supported by all MongoDB versions. 

      Motivation

      Who is the affected end user?

      Backend, Fullstack developer

      How does this affect the end user?

      Users can now easily index and query UUID and null fields.

      How likely is it that this problem or use case will occur?

      Main path

      If the problem does occur, what are the consequences and how severe are they?

      Previously, users had to store, index and query their UUIDs and nulls as 'string' fields to use with Atlas Search. This results in data duplication, results in poor code hygiene, and is not acceptable for users who use strictly typed languages. 

      Is this issue urgent?

      Does this ticket have a required timeline? What is it?

      Is this ticket required by a downstream team?

      Needed by Atlas Search

      Is this ticket only for tests?

      Functional improvement

      Acceptance Criteria

      Users must be able to query for

      • UUID types using the equals and in operator
      • null using the equals operator

      Additionally, users must be able to specify UUID fields for Atlas Search sorting.

       

            Assignee:
            Unassigned Unassigned
            Reporter:
            sara.akram@mongodb.com Sara Akram (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: