[SERVER-62025] Implement fallback mechanism for queries which aren't supported in CQF Created: 13/Dec/21  Updated: 29/Oct/23  Resolved: 17/Jun/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: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
is duplicated by SERVER-62440 Add test-only flag to enable supporte... Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2022-01-10, QO 2022-01-24, QO 2022-05-02, QO 2022-05-16, QO 2022-05-30, QO 2022-06-13, QO 2022-06-27
Participants:
Linked BF Score: 60

 Description   

This includes unsupported query operators, command options, or metadata (e.g. index types). Exact details are listed in the Supported Features spreadsheet.



 Comments   
Comment by Githook User [ 17/Jun/22 ]

Author:

{'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-62025 Skip test for builders that force the classic engine
Branch: master
https://github.com/mongodb/mongo/commit/4c3b1e42d06ed28752f23505956b71834c834935

Comment by Githook User [ 16/Jun/22 ]

Author:

{'name': 'Nicholas Zolnierz', 'email': 'nicholas.zolnierz@mongodb.com', 'username': 'nzolnierzmdb'}

Message: SERVER-62025 Only use CQF path for eligible queries and fallback to classic optimizer otherwise
Branch: master
https://github.com/mongodb/mongo/commit/43cf2cd5f8ac1144e24323ef183ee21a024a9de9

Generated at Thu Feb 08 05:53:57 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.