[DOCS-11834] Docs for SERVER-34138: Allow change stream against non-existent DB+collection in sharded cluster Created: 26/Jun/18  Updated: 26/Jun/18  Resolved: 26/Jun/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 4.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34138 Allow change stream against non-exist... Closed
Participants:
Days since reply: 5 years, 33 weeks, 1 day ago

 Description   

----------------------------

Original Description

Description:

In 3.6, a change stream could be opened on a non-existent collection in a replica set or sharded cluster, but only if the database already existed. After this commit, a stream can be opened on a non-existent collection before the enclosing database has been created.

Engineering Ticket 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".

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)



 Comments   
Comment by Kay Kim (Inactive) [ 26/Jun/18 ]

Per discussion in ticket DOCS-11098

Generated at Thu Feb 08 08:03:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.