[SERVER-56730] Improve Change Streams API timestamp to millisecond or greater precision Created: 06/May/21  Updated: 29/Oct/23  Resolved: 12/Apr/22

Status: Closed
Project: Core Server
Component/s: Change streams
Affects Version/s: None
Fix Version/s: 6.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Chris Kramer Assignee: Backlog - Query Execution
Resolution: Fixed Votes: 0
Labels: pm1950-m4
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-52254 Enable feature flag for Improved chan... Closed
Related
is related to JAVA-4045 Change Events with more accurate time... Closed
Assigned Teams:
Query Execution
Backwards Compatibility: Fully Compatible
Sprint: Query Execution 2021-05-31, Query Execution 2021-06-14
Participants:

 Description   

We use Qlik Replicate to do change data capture on other data sources to our data warehouse. When using it from MongoDB, we found that they are using the Change Streams API which only has to the second precision. We'd like to get an enhancement to allow millisecond or greater precision.



 Comments   
Comment by Bernard Gorman [ 12/Apr/22 ]

Hi chris.kramer@digikey.com,

As of MongoDB 6.0, change streams will report a new millisecond-precisions field called wallTime - along with several new DDL event types - when the new showExpandedEvents parameter is set to true. Please consult our forthcoming 6.0 documentation for full details. Note that change stream events will continue to be sorted in logical clusterTime order, and as such on a sharded cluster events are not always guaranteed to be reported in strictly increasing wallTime order.

Best regards,
Bernard

Comment by Edwin Zhou [ 10/May/21 ]

Hi chris.kramer@digikey.com

Thank you for your improvement request on changeStreams. We're assigning this ticket to the appropriate team to be evaluated against our currently planned work. Updates will be posted on this ticket as they happen.

Best,
Edwin

Generated at Thu Feb 08 05:40:03 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.