[SERVER-30512] Ensure all changeStreams field names match the spec Created: 03/Aug/17 Updated: 30/Oct/23 Resolved: 15/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Siyuan Zhou |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Repl 2017-08-21 |
| Participants: |
| Description |
|
Several of the names of the arguments or fields in return values for change streams have had multiple renames as the design has stabilized. For instance the argument fullDocument:'lookup' was recently renamed fullDocument:'updateLookup'. We should make that change, and compare the inputs/outputs of every piece of changeNotification that has been committed matches the current version of the spec. |
| Comments |
| Comment by Githook User [ 15/Aug/17 ] |
|
Author: {'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou'}Message: |
| Comment by Githook User [ 15/Aug/17 ] |
|
Author: {'username': 'visualzhou', 'email': 'siyuan.zhou@mongodb.com', 'name': 'Siyuan Zhou'}Message: |
| Comment by Spencer Brody (Inactive) [ 09/Aug/17 ] |
|
FYI fullDocument: 'none' was also renamed fullDocument: 'default' |