Added
- Add simple python client example @wslulciuc
- Display dataset versions in web UI 🎉 @phixMe
- Display runs and run facets in web UI 🎉 @phixMe
- Facet formatting and highlighting as Json in web UI @phixMe
- Add option for
docker/up.sh
to run in the background @rossturk - Return
totalCount
in lists of jobs and datatsets @phixMe
Changed
- Change type column in
dataset_fields
table toTEXT
@wslulciuc - Set
ZonedDateTime
parsing to support optional offsets and default to server timezone @collado-mike
Fixed
Job.location
andSource.connectionUrl
should be in URI format on write @OleksandrDvornik- Z-Index fix for nodes and edges in lineage graph @phixMe
- Format of the index files for web UI @phixMe
- Fix OpenLineage API to return correct response codes for exceptions propagated from async calls @collado-mike
- Stopped overwriting nominal time information with nulls @mobuchowski
Removed
WriteOnly
clients forjava
andpython
. Before OpenLineage, we added aWriteOnly
implementation to our clients to emit calls to a backend. Abackend
enabled collecting raw HTTP requests to an HTTP endpoint, console, or file. This was our way of capturing lineage events that could then be used to automatically create resources on the Marquez backend. We soon worked on a standard that eventually became OpenLineage. That is, OpenLineage removed the need to make individual calls to create a namespace, a source, a datasets, etc, but rather accept an event with metadata that the backend could process. @wslulciuc