Fix Unix epoch time display in case of null endedAt
value
#2647
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.
Problem
In the case of a fresh instance of Marquez (e.g., a new user experimenting with a quickstart), using cURL to post a start event by itself causes the
runs
component to display the Unix epoch time in the ENDED AT column.Solution
This makes displaying the
endedAt
value conditional on there being adurationMs
value greater than 0. Otherwise, it will display 'N/A'.One-line summary: Fixes Unix epoch time display in case of null
endedAt
value.Closes: #2646
Checklist
CHANGELOG.md
(Depending on the change, this may not be necessary)..sql
database schema migration according to Flyway's naming convention (if relevant)