[DOCS-12540] Docs for SERVER-39302: Change streams should always use the simple collation when no explicit collation is provided Created: 12/Mar/19  Updated: 13/Nov/23  Resolved: 28/May/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.1.9, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

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

Issue Links:
Documented
documents SERVER-39302 Change streams should always use the ... Closed
Participants:
Days since reply: 4 years, 37 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools

 Description   

Description

Description:

Previously, single-collection change streams inherited the default collation of the collection on which they were opened. This makes little sense, given that we are not actually querying documents from that collection; a so-called single-collection change stream is just a filter on the oplog for that namespace. This behaviour unintuitively restricts the client's ability to resume the stream, and is inconsistent with the semantics of whole-db and whole-cluster streams - both of which always use the simple collation unless explicitly provided with an alternative.

To ensure stability with respect to the change stream's collation, and to guarantee that we can resume the stream in all circumstances, this ticket changes the behaviour of single-namespace streams to be consistent with whole-db and whole-cluster streams. All change streams will now use the simple collation unless a different collation is explicitly provided with the request when opening the stream.

Engineering Ticket Description:

Currently, single-namespace change streams inherit the default collation of the collection for which they are filtering. This makes little sense, given that we are not actually querying documents from that collection; a so-called single-namespace change stream is, in reality, simply a filter on the oplog for that namespace. The current behaviour unintuitively restricts the client's ability to resume the stream, and is inconsistent with the semantics of whole-db and whole-cluster streams - both of which always use the simple collation unless explicitly provided with an alternative.

To ensure stability with respect to the change stream's collation, and to guarantee that we can resume the stream in all circumstances, we should change the behaviour of single-namespace streams to be consistent with whole-db and whole-cluster streams.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 28/May/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-12540,DOCS-12588: db.coll.watch() default collation, changestream events clusterTime and sharded cluster txns
Branch: master
https://github.com/mongodb/docs/commit/6bf989fb89663fa1e27ccfd9c7e6b7abd59b95a9

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