[DOCS-16060] [Atlas Search] changes in SERVER-75010: Implement no-op planShardedSearch in 5.0 Created: 21/Apr/23  Updated: 29/Oct/23  Resolved: 03/Oct/23

Status: Closed
Project: Documentation
Component/s: Atlas
Affects Version/s: None
Fix Version/s: 5.0.18, 4.4.22

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Kanchana Sekhar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-75010 Implement no-op planShardedSearch in 5.0 Closed
Participants:
Days since reply: 18 weeks, 2 days ago
Story Points: 1

 Description   
Original Downstream Change Summary

`$search` queries with a specified `sort` in sharded clusters will now fail instead of silently return incorrect results.

Description of Linked Ticket

Currently planShardedSearch is only implemented in 6.0+. Thus when a sharded cluster receives a $search query with sort, it does not support merge sorting on $searchSortValues as mongos never got a sortSpec from mongot, resulting in incorrect query results (potentially not sorted results).

The task of this ticket is to send a planShardedSearch request in sharded cluster in 5.0 to mongot, indicating to mongot that mongos does not support sort. Mongot will respond with an error if the query contains a sort, causing mongos to error out. This will solve the problem described above by returning an error rather than silently returning incorrect results.



 Comments   
Comment by Kanchana Sekhar [ 02/Oct/23 ]

PR: https://github.com/10gen/cloud-docs/pull/4925

Comment by Lauren Tran [ 28/Sep/23 ]

Moving this to Needs Triage with the component Atlas because the ticket addresses an Atlas docs page: https://www.mongodb.com/docs/atlas/atlas-search/query-syntax/#mongodb-pipeline-pipe.-search

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