[SERVER-41237] Ban $graphLookup on sharded foreign collections Created: 20/May/19  Updated: 29/Oct/23  Resolved: 18/Jun/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 4.1.11
Fix Version/s: 4.2.0-rc2, 4.3.1

Type: Bug Priority: Major - P3
Reporter: Ian Boros Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
is related to SERVER-58073 Allow $graphLookup against a sharded ... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2
Sprint: Query 2019-06-17, Query 2019-07-01
Participants:

 Description   

Looks like we left this in while working on sharded lookup.

 



 Comments   
Comment by Githook User [ 19/Jun/19 ]

Author:

{'name': 'Ian Boros', 'email': 'puppyofkosh@gmail.com', 'username': 'puppyofkosh'}

Message: SERVER-41237 Re-ban $graphLookup against a sharded collection
Branch: v4.2
https://github.com/mongodb/mongo/commit/113260628583714bea96aa79fdf70937f9edcae7

Comment by Githook User [ 18/Jun/19 ]

Author:

{'name': 'Ian Boros', 'email': 'puppyofkosh@gmail.com', 'username': 'puppyofkosh'}

Message: SERVER-41237 Re-ban $graphLookup against a sharded collection
Branch: master
https://github.com/mongodb/mongo/commit/08be6c5794d704154cf2b89181bb734c6e777ac4

Comment by Ian Boros [ 20/May/19 ]

I think we should do this before the release.

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