Track asset selection on data product input port from Data Product Descriptor #87
giulioscotti
started this conversation in
Ideas
Replies: 1 comment
-
Makes sense to me. @giulioscotti, go ahead and create an RFC and set yourself as the champion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, when you track in the Data Product Descriptor the dependency of an input port from the output port of another product in the mesh or from a source system referenced from an external Data Catalog, you have no way to explicitely select a subset of assets read by the input port.
The dependsOn property only allows to track the fqn of the upstream input port or external system.
This is a limitation because it prevents from understanding which specific assets (es: tables, views..) the data product actually reads data from. When the output port of the upstream product or the source system contains many assets, it's not easy to identify the useful ones.
It's required to extend Data Product Descriptor Specification to allow track this list of source assets in the descriptor file.
Beta Was this translation helpful? Give feedback.
All reactions