Change streams and Triggers for Time Series Collections
Add Change streams and Trigger capabilities to Time Series Collections.
Current Limitations don't allow this.
https://docs.mongodb.com/manual/core/timeseries/timeseries-limitations/#change-streams
Alexander
shared this idea
-
David
commented
This feature would be critical for our infrastructure. We have two different applications working on sensor data, both of which support offline functionality. As a result, we must maintain three separate databases, two of which are typically beyond our control.
The only reliable way to manage time series data and ensure full synchronization between databases would be to use change streams or, as we are doing right now, periodically query the entire database for marked unsynchronized data when we have connection to the database server. However, this approach is not only incredibly slow but also resource-intensive for both the data and the infrastructure we currently have.
We will periodically monitor the status of this feature request as we aim to migrate our infrastructure to MongoDB Atlas and streamline the development of our application.
Thank you in advance
-
Still no ETA for this, but's it's on the roadmap
-
Anthony Uphof
commented
Any Update on this ?
-
Michael
commented
I was super excited to use timeseries collections, and built a prototype, which didn't work. I use change streams all over our app, for real-time updates. After much hair pulling, finally found that timeseries collections can't be "watched". Uggh! This is the perfect use case for them, updates from many places and a beautiful way to stream (and filter) those changes for real time processing. Please please please implement this!
