-
Type:
New Feature
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Component/s: None
-
None
-
Builder Changes Needed
-
Summary
What is the problem or use case, what are we trying to achieve?
Customers use embeddedDocuments to model one-to-many relationships, however, this results in functionality gaps with $search.facet and $search.sort, which results in facet counts and sort order being inaccurate because Search doesn't consider which embeddedDocuments are matching.
New Syntax for $search and $searchMeta: https://docs.google.com/document/d/1urn6HL-StfIjdRRX0pdDvcVJGQcvg-AVFL9zpMcY2TA/edit?tab=t.0
Motivation
Who is the affected end user? Search developer
Who are the stakeholders?
How does this affect the end user?
Blocked from using MongoDB Search, or poor performance using $group or $sort with $filter workaround.
How likely is it that this problem or use case will occur?
Common when using embeddedDocuments in Search.
If the problem does occur, what are the consequences and how severe are they?
Poor performance, functional gaps in customer application.
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
Unsure
Acceptance Criteria
Within all builders, introduce the ability to:
- use new parameter within $search.facet.facets.[i].embeddedDocument
- use new parameter within $search.sort.[i].embeddedDocument
Launch timeline: Sept 1, 2026. Builder support can be fast follow.
- split to
-
INTPYTHON-1036 MongoDB Search embeddedScoped-facet and sort
-
- Needs Triage
-
-
CSHARP-6152 MongoDB Search embeddedScoped-facet and sort
-
- Blocked
-
-
JAVA-6270 MongoDB Search embeddedScoped-facet and sort
-
- Blocked
-
-
PHPLIB-1924 MongoDB Search embeddedScoped-facet and sort
-
- Blocked
-