[SERVER-39302] Change streams should always use the simple collation when no explicit collation is provided Created: 31/Jan/19 Updated: 29/Oct/23 Resolved: 12/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Aggregation Framework |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Bernard Gorman | Assignee: | Bernard Gorman |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Minor Change | ||||||||||||||||
| Sprint: | Query 2019-03-11, Query 2019-03-25 | ||||||||||||||||
| Participants: | |||||||||||||||||
| 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. |
| Comments |
| Comment by Githook User [ 12/Mar/19 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |
| Comment by Githook User [ 12/Mar/19 ] |
|
Author: {'name': 'Bernard Gorman', 'email': 'bernard.gorman@gmail.com', 'username': 'gormanb'}Message: |