feat: add metadata timestamp (CM-868) #3814
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Add
metadata.commit_timestampto the Kafkaactivitiestopic payload to align with the structure of othertopics coming from Sequin.
Background
All topics from Sequin have this structure:
{ "metadata": { "commit_timestamp": "2025-03-17T02:51:12.741208Z" }, "record": { ... } }However, the activities topic is pushed directly by data-sink-worker (not via Sequin), so it was missing the
metadata field.
Changes:
Also on the activities message now we have the structure:
{ ....., "metadata": { "commit_timestamp": "2025-03-17T02:51:12.741208Z" }, }Note
Low Risk
Small, additive payload change (new metadata field) with minimal logic changes; main risk is downstream consumers that assume a fixed message schema.
Overview
Activity messages emitted from
insertActivitiesnow include ametadata.commit_timestampfield (ISO timestamp) before being sent to the activities queue/Kafka, and logs were updated to include the new timestamp when dispatching.Written by Cursor Bugbot for commit 5652a17. This will update automatically on new commits. Configure here.