[SERVER-37491] Allow for creating a view in one database sourced from a collection in another database Created: 05/Oct/18  Updated: 06/Dec/22

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

Type: Improvement Priority: Minor - P4
Reporter: Harshad Dhavale Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Query Optimization
Participants:
Case:

 Description   

Currently, it is not possible to create a view in one database sourced from a collection in another database. As mentioned in db.createView()  documentation, the `source` parameter for the view does not include the database name and implies the same database as the view to create. It is implicitly assumed (and in fact, required), that the source collection must be in the same database as the view being collected.

This is a feature-improvement request, to allow for creating a view in one database sourced from a collection in another database.



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

I have a case here, where data across different stages is modified until usable for the use cases. Following security best-practices, we want to have only schema-wide access to users. That means, we have a view layer (i.e. different database) with refined data, where read-only privileges are provided. These users do not have access privileges to underlying stages.

Comment by Asya Kamsky [ 12/Oct/18 ]

harshad.dhavale why is this desirable?

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