[SERVER-34935] Support cross-database lookup Created: 10/May/18  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: None

Type: New Feature Priority: Major - P3
Reporter: Adinoyi Omuya Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 34
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29159 Allow "from" collection of $lookup to... Closed
Assigned Teams:
Query Optimization
Sprint: Query 2018-12-03
Participants:
Case:

 Description   

This will increase the expressiveness of the aggregation pipeline and allow new applications to be supported by MongoDB.

Work should include banning $lookup stages that reference a foreign DB from non-materialized view definitions.



 Comments   
Comment by Christian Kurze (Inactive) [ 27/Aug/19 ]

Is there a tentative date when this issue moves back into active development?

I have a case here, where data across different stages is modified until usable for the use cases. It involves some $lookups and different databases would be great for easier managment of privileges (e.g. read to the whole refined data, but no access to underlying stages).

Comment by Charlie Swanson [ 03/Dec/18 ]

Unfortunately devin.hilly has rotated off the query team before we could get this fully working so I'm moving this back onto the backlog user to be picked up in a later sprint.

 

The linked code review has the details on what we did get working and what still needs to be done/investigated. Thanks devin.hilly!

Comment by Charlie Swanson [ 16/Nov/18 ]

Tentatively bringing this into the sprint and assigning to Devin. The scope here will probably have to be constrained to unsharded deployments to avoid breaking things, as a start.

Comment by Adinoyi Omuya [ 11/May/18 ]

Nope, thanks for the update.

Comment by Charlie Swanson [ 11/May/18 ]

adinoyi.omuya did you mean to assign this to yourself?

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