[DRIVERS-2803] Driver support using token field type with equals, range and in operators should add support Created: 02/Jan/24 Updated: 16/Jan/24 |
|
| Status: | Scheduled |
| Project: | Drivers |
| Component/s: | None |
| 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: |
|
||||||||||||||||||||
| Epic Link: | CLOUDP-217393 | ||||||||||||||||||||
| Driver Changes: | Builder Changes Needed | ||||||||||||||||||||
| Quarter: | FY25Q1 | ||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||
| Description |
Summary_Users will be able to use token for unanalyzed text search use cases (e.g. exact match / filtering). Any driver that does not currently allow passing strings into `equals.value`, `range.gt`/`range.lt` and `in.value` fields should add support. This functionality is supported on all MDB versions.
This includes but may not be limited to: MotivationWho is the affected end user?Full-stack developer, Sales-sold and self-serve How does this affect the end user?_Pain Point: X% of users who want to perform exact matching can’t easily get the search results they want. If the problem does occur, what are the consequences and how severe are they?In addition to improving the exact matching user experience in Atlas Search, there are also performance benefits to offering a first-class solution to exact matching, observed in multiple customer cases since token support for equals/in/range was released “quietly” in September 2023: Is this issue urgent?fy2025Q1 For detailed information: Product Description: Token for unanalyzed text search |
| Comments |
| Comment by Tom Selander [ 09/Jan/24 ] |
|
Triage: Let's try to prioritize this for the builders for Q1 for any teams that can squeeze it in. |
| Comment by Sara Akram [ 02/Jan/24 ] |
|
cc. rachelle.palmer@mongodb.com, amy.jian@mongodb.com, jessica.sigafoos@mongodb.com, alice.neff@mongodb.com |