[SERVER-83419] Invalid collection name is not valid for search pushdown Created: 17/Nov/23  Updated: 30/Nov/23  Resolved: 30/Nov/23

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

Type: Bug Priority: Major - P3
Reporter: Zixuan Zhuang Assignee: Alberto Massari
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2023-11-27, QE 2023-12-11
Participants:
Linked BF Score: 130

 Description   

For $search in sub-pipeline, we check if it is eligible to pushdown here, but when the collection name is not valid we skip the pushdown. In this case, DocumentSourceSearch won't be pushed down into SBE and also not desugared.



 Comments   
Comment by Githook User [ 29/Nov/23 ]

Author:

{'name': 'Alberto Massari', 'email': 'alberto.massari@mongodb.com', 'username': 'albymassari'}

Message: SERVER-83419 Aggregation stages on missing collections are pushed down to SBE
Branch: master
https://github.com/mongodb/mongo/commit/aba841cbb6acde79ce30ccabcbc614be7dc0c216

Comment by Ted Tuckman [ 21/Nov/23 ]

I looked into this a little bit. It seems to me like this isn't actually a search specific issue. Right now from the code linked above that SBE will bail out if there is a $unionWith on a collection that doesn't exist. It seems to me that SBE should be able to deal with this case and treat it as a normal plan that will immediately return EOF. Discussed a little bit with mihai.andrei@mongodb.com who came to the same conclusion. Putting this back up for triage on QE. The linked BF is hot, so would be good for someone more familiar with SBE to see if there's a simple way of addressing this.

CC amr.elhelw@mongodb.com 

Comment by Chris Hutchinson [ 17/Nov/23 ]

ted.tuckman@mongodb.com - could you please find someone to work on this ticket as Zixuan will be out for two weeks from 11/20

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