plain-arm-6774
06/24/2020, 5:09 AMsteep-airplane-62865
06/25/2020, 6:03 AMsteep-airplane-62865
06/25/2020, 6:05 AMsteep-airplane-62865
06/25/2020, 6:06 AMplain-arm-6774
06/25/2020, 5:42 PMplain-arm-6774
06/25/2020, 5:44 PMplain-arm-6774
06/29/2020, 5:34 PMsteep-airplane-62865
06/29/2020, 8:52 PMtable
, database
and the instance
and track the relationship between them. Short answer, DataHub doesn't have that support right now.steep-airplane-62865
06/29/2020, 8:54 PMDatabase -> DataPlatform
This is not quite correct as well. DataPlatform
is not an entity that uniquely defines a database. You can check DataPlatformUrn
. It's actually an entity to uniquely define a data platform type like mysql, hdfs etc. The purpose of that is different than what you thought originally.plain-arm-6774
06/30/2020, 12:04 AMtable
, database
, instance
(each with appropriate properties and relationships), correct?
Short answer, DataHub doesn't have that support right now.
Does this mean that the above solution works but is not as ideal as adding explicit data models for each of the data asset types?bumpy-keyboard-50565
06/30/2020, 9:48 PM<database>.<table>
as a dataset, each identified by an URN of {platform, name, fabric}
(fabric
is used to denote different environment, e.g. prod
vs staging
). For multiple deployments of a single dataset (e.g. replicas of MySQL tables), we're introducing a new entity called DatasetInstance
. We do plan to open source that entity models at some point too.plain-arm-6774
06/30/2020, 10:03 PM