-
Type: Improvement
-
Resolution: Gone away
-
Priority: Critical - P2
-
Affects Version/s: None
-
Component/s: Server
-
Labels:
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.