[DRIVERS-2809] Drivers Support for indexing and querying on UUID and null datatype Created: 16/Jan/24  Updated: 23/Jan/24

Status: Scheduled
Project: Drivers
Component/s: Index Management
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Sara Akram Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CSHARP-4938 Drivers Support for indexing and quer... Blocked
split to JAVA-5299 Drivers Support for indexing and quer... Blocked
split to PHPORM-135 Drivers Support for indexing and quer... Investigating
Epic Link: CLOUDP-170171
Driver Changes: Builder Changes Needed
Quarter: FY25Q1
Downstream Changes Summary:

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
Driver Compliance:
Key Status/Resolution FixVersion
CSHARP-4938 Blocked
JAVA-5299 Blocked
PHPORM-135 Investigating

 Description   

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.

 



 Comments   
Comment by Sara Akram [ 16/Jan/24 ]

cc. rachelle.palmer@mongodb.com, jessica.sigafoos@mongodb.com, amy.jian@mongodb.com

Generated at Thu Feb 08 08:26:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.