[KAFKA-251] Save cluster time when it was inserted or updated Created: 22/Sep/21  Updated: 04/May/22  Resolved: 28/Sep/21

Status: Closed
Project: Kafka Connector
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Unknown
Reporter: Juan Soto (Inactive) Assignee: Ross Lawley
Resolution: Duplicate Votes: 0
Labels: internal-user
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates KAFKA-229 Monitor the Kafka Source Connector La... Closed

 Description   

Hello team,

At the moment the UpdateOneTimestampsStrategy and UpdateOneBusinessKeyTimestampStrategy are adding two fields _insertedTS and _modifiedTS. These fields are getting the timestamp from kafka connect server. It will be nice if we can also add time from MongoDB cluster. 

With this information it will be easier to understand the lag between kafka and MongoDB. 

Thanks,

Juan



 Comments   
Comment by Ross Lawley [ 28/Sep/21 ]

Hi juan.soto,

I'm marking this as a duplicate of KAFKA-229 - which is the lag / monitoring ticket.

Adding extra fields to existing WriteModel strategies would impact users that already use those strategies, so may not be the best course of action.

Ross

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