[DOCS-11555] Document limitation of change streams when watching a non-existent collection Created: 06/Apr/18  Updated: 30/Oct/23  Resolved: 29/Nov/22

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Critical - P2
Reporter: Asya Kamsky Assignee: Jeffrey Allen
Resolution: Gone away Votes: 0
Labels: reopened
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 10 weeks, 1 day ago
Epic Link: DOCSP-26173

 Description   

Due to SERVER-33944 change streams opened against non-existent collections must specify the same collation as the collection itself will have when it's created.

If default collation is used, this won't be an issue. But if collection has non-default collation specified (or will have it specified) then change stream should specify the same collation explicitly to avoid running into SERVER-33944 in a sharded cluster.

Note that if this bug is triggered, the application can simply resume, this workaround is to avoid even having that be necessary.



 Comments   
Comment by Jeffrey Allen [ 29/Nov/22 ]

With the work done in SERVER-39302, this behavior has gone away and no longer needs to be documented.

Comment by Sarah Olson [ 31/Oct/22 ]

Topic: change streams, non-default collations

See related Server tickets.

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