[SERVER-29134] Support returning all change notifications for a database in a sharded cluster Created: 11/May/17  Updated: 30/Oct/23  Resolved: 11/Apr/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: Crystal Horn Assignee: Nicholas Zolnierz
Resolution: Fixed Votes: 0
Labels: todo_in_code
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
is documented by DOCS-11602 Docs for SERVER-29134: Support return... Closed
Related
is related to SERVER-31847 Allow sharded $changeStream to contin... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2018-04-09, Query 2018-04-23
Participants:

 Description   

This is just tracking the work to make this functionality available on a sharded cluster. The work to support this on a single replica set is tracked by SERVER-33918



 Comments   
Comment by Githook User [ 11/Apr/18 ]

Author:

{'email': 'nicholas.zolnierz@mongodb.com', 'name': 'Nick Zolnierz', 'username': 'nzolnierzmdb'}

Message: SERVER-29134: Support change streams on an entire database in a sharded cluster
Branch: master
https://github.com/mongodb/mongo/commit/fff261ac550155065fce4b7b1529061f18980599

Comment by Spencer Brody (Inactive) [ 24/Jul/17 ]

Notifications on a database have been tentatively cut from 3.6 to ensure that single-collection change streams can be delivered on time.

If we have extra time towards the end of the release cycle we may try to revive this work and get it in

Generated at Thu Feb 08 04:19:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.