[SERVER-62034] Ensure CQF path is not enabled for pipeline prefixes or sub-pipelines Created: 13/Dec/21  Updated: 29/Oct/23  Resolved: 31/Oct/22

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

Type: Task Priority: Major - P3
Reporter: Nicholas Zolnierz Assignee: Ben Shteinfeld
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-71343 Complete TODO listed in SERVER-62034 Closed
Backwards Compatibility: Fully Compatible
Sprint: QO 2022-10-03, QE 2022-10-17, QO 2022-10-31
Participants:

 Description   

This ticket covers any necessary code changes and testing for two kinds of queries: sub-pipelines (e.g. the subpipeline run by $lookup or $graphLookup against the foreign collection) and pipeline prefixes, meaning the parts of the agg pipeline which are handled by the find layer.

We may be able to support these queries if the sub-pipeline or pipeline prefix is entirely supported in CQF. But, the user story is confusing and it adds to the testing surface area. This ticket may not result in any code changes but we should verify that we use the classic query system.



 Comments   
Comment by Githook User [ 31/Oct/22 ]

Author:

{'name': 'Ben Shteinfeld', 'email': 'ben.shteinfeld@mongodb.com', 'username': 'bshteinfeld'}

Message: SERVER-62034 Prevent hybrid CQF for pipeline prefixes and subpiplines
Branch: master
https://github.com/mongodb/mongo/commit/e47f6574153c81f6995c5aaf238171e4cde2b5ee

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