[SERVER-38079] Change Streams without Replication Created: 11/Nov/18 Updated: 06/Dec/22 Resolved: 14/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Minor - P4 |
| Reporter: | Daniel Faust | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Description |
|
Allow applications to access real-time data changes via change streams without requiring the database to be a replica set or sharded cluster.
The issue is that in the case of a small database, for example a 20 MB database storing the current status of devices in a local area network, like environment sensors, it is not feasible to enable replication if it is not required for the data, because that would force the creation of a 1 GB oplog.
|
| Comments |
| Comment by Kelsey Schubert [ 14/Nov/18 ] |
|
Thanks for your interest and confirming. |
| Comment by Daniel Faust [ 14/Nov/18 ] |
|
Yes, it is a duplicate. My apologies. |
| Comment by Asya Kamsky [ 14/Nov/18 ] |
|
Duplicate of |