Julien Le Dem

OpenLineage has a [column-level lineage facet](https://github.com/OpenLineage/OpenLineage/blob/main/spec/facets/ColumnLineageDatasetFacet.json). Marquez could leverage this to implement a column-level lineage endpoint. Existing: ``` GET /lineage?nodeId=dataset:food_delivery:public.delivery_7_days ``` returns all the reachable nodes up to a given...

Add extension point for lineage event validation

4

Some users need to be able to validate lineage events. The goal of this feature is to make it easy for them to add validation logic to incoming events and...

Ability to DELETE jobs and datasets

1

When jobs or datasets are deleted (or renamed) we need a way to tell Marquez that they don't exist anymore so that they don't clutter the lineage view. It would...

The REST API could be a layer on graphql.

The logback appender we use for sentry depends on a sentry client version that is > 2 years old. We should update our dependency, absorbing the logback appender, if necessary.

When Inputs are not provided it should not be interpreted as "no input"

The lineage api needs explicit display names and labels as well as groups to be used in the lineage graph representation

2

- explicit definition of a display name - explicit description of the structure of the name - explicit definition of groups. example/strawman: ``` Name: {db name}.public.{table name} { structuredName: [...