-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(ingest): set DataProcessInstance created ts to start time #6566
Conversation
In the dataJob runs tab (which shows dataProcessInstances), the "Time" column displays the `dataProcessInstanceProperties.created` timestamp. This change makes the emitter actually show the real start times when provided.
@@ -164,7 +164,7 @@ def emit_process_start( | |||
for mcp in template_object.generate_mcp(): | |||
self._emit_mcp(mcp, emitter, callback) | |||
|
|||
for mcp in self.generate_mcp(): | |||
for mcp in self.generate_mcp(created_ts_millis=start_timestamp_millis): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should have been there in the first place! Nice change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. No tests to update?
Our tests ignore the timestamps so they remain unchanged. At some point we will need to add proper tests for this stuff though |
In the dataJob runs tab (which shows dataProcessInstances), the "Time" column displays the
dataProcessInstanceProperties.created
timestamp. This change makes the emitter actually show the start times when provided.Slack ref: https://datahubspace.slack.com/archives/CUMUWQU66/p1669108847712609?thread_ts=1669020230.808929&cid=CUMUWQU66
Checklist