[SERVER-67371] Do not use CQF path for find commands with additional options that aren't supported in agg Created: 17/Jun/22  Updated: 29/Oct/23  Resolved: 15/Aug/22

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 6.1.0-rc0

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Ruslan Abdulkhalikov (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-66788 [CQF] Add ability to retrieve index k... Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2022-08-08, QO 2022-08-22
Participants:

 Description   

The following options are not checked when translating from find->agg->ABT, but they will fail in agg:

  • returnKey
  • singleBatch
  • tailable cursors
  • sort (find command only, aggregation stage is already treated as unsupported)

We may be able to allow these options once the translation to ABT does not need to go through aggregate.



 Comments   
Comment by Hana Pearlman [ 18/Jul/22 ]

nicholas.zolnierz@mongodb.com Yep! Sounds good.

Comment by Nicholas Zolnierz [ 15/Jul/22 ]

hana.pearlman@mongodb.com is it ok if we prioritize this? Apparently there's an internal query during a sharded cluster init that uses the noCursorTimeout option, and fails when we try to translate the find to agg.

Generated at Thu Feb 08 06:07:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.