[DOCS-10792] is there any way to record changes of document data, after the implementation of oplog Created: 15/Sep/17 Updated: 29/Oct/23 Resolved: 15/Sep/17 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | w j | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 6 years, 21 weeks, 5 days ago |
| Description |
|
I'd like to know is there any way to record changes of document data, after the implementation of oplog |
| Comments |
| Comment by Ravind Kumar (Inactive) [ 15/Sep/17 ] |
|
If you have further questions on implementing oplog tailing, please visit out google group for help from our community support engineers. |
| Comment by Ravind Kumar (Inactive) [ 15/Sep/17 ] |
|
Thanks for filing a DOCS ticket. Since the OPLOG is a capped collection, you can open a tailable cursor to the collection to pull data in real-time. That said, if you hang on, MongoDB 3.6 will feature a Notifications API. You can read more about it on this blog post by one of our own engineers, Jesse Jiryu Davis. |