-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Component/s: None
-
None
-
Builder Changes Needed
-
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:
C#
_
Motivation
Who 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.
Before State: To meet their application requirements of performing exact match searches, customers have to index their text fields as Atlas Search string field mapping types configured with the keyword analyzer.
After State: Users can configure a token field mapping to meet the needs of their unanalyzed text search use cases. _
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
- related to
-
CSHARP-5429 Support strings with range operator for atlas search
- Investigating
- split to
-
JAVA-5289 Driver support using token field type with equals, range and in operators should add support
- Backlog
-
PHPORM-129 Driver support using token field type with equals, range and in operators should add support
- Backlog
-
CSHARP-4926 Driver support using token field type with equals operator
- Closed
-
CSHARP-5429 Support strings with range operator for atlas search
- Investigating