* feat(Azkaban entities): RFC for Azkaban Flows and Jobs
* Update to pivot to data job and flow as an entity and address comments
* Update urn definitions and address comments
* address minor comments
* feat(field-level-lineage): RFC for field-level-lineage
RFC for field level lineage or column level lineage.
* feat(field-level-lineage): RFC for field-level-lineage
Update RFC to include DatasetField as a first class entity
* feat(field-level-lineage): RFC for field-level-lineage
fixing a typo
This seems helpful to reviewers (and probably also the author). Motivation is too high level to be able to properly review a design. We need a clear set of requirements to review the design against.
* Create RFC for ML Model
* Add ml model graph file
* add link to graph
* Add high level design for ML model
* ai->ml
* Rename 000-ml_models.md to README.md
* Add link to RFC PR
* Update README.md
* address some comments
* Delete ml_model_graph.png
* add ML Model graph
* Address reviewer comments
* Address more comments
* Update README.md
* Rename docs/rfc/active/000-ml_models/README.md to docs/rfc/active/1812-ml_models/README.md
* Delete high_level_design.png
* Delete ml_model_graph.png
* Add files via upload
Co-authored-by: Mars Lan <mars.th.lan@gmail.com>
Other repos have similar RFC processes (though they seem to have a separate repo for their RFC docs).
This provides a more structured way for contributors to make siginficant design contributions.
https://github.com/linkedin/datahub/issues/1692