[SERVER-34138] Allow change stream against non-existent DB+collection in sharded cluster Created: 26/Mar/18  Updated: 29/Oct/23  Resolved: 29/Apr/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

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

Issue Links:
Backports
Depends
is depended on by SERVER-34283 Remove ban on whole-database change s... Closed
Documented
is documented by DOCS-11834 Docs for SERVER-34138: Allow change s... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6
Sprint: Query 2018-04-23, Query 2018-05-07
Participants:

 Description   

Opening a change stream against a non-existent db/collection in a single replica set works fine, however the same test in a sharded cluster fails with "InvalidNamespace".



 Comments   
Comment by Githook User [ 29/Apr/18 ]

Author:

{'email': 'bernard.gorman@gmail.com', 'username': 'gormanb', 'name': 'Bernard Gorman'}

Message: SERVER-34138 Allow change stream to be opened against non-existent DB and collection in sharded cluster
Branch: master
https://github.com/mongodb/mongo/commit/793e59f11b558db3d833a12ec23bbacc359011a1

Comment by Ian Whalen (Inactive) [ 11/Apr/18 ]

as part of this ticket please validate that we aren't doing implicit database creation.

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