A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

Ok, if I understood correctly, in case of a renamed table we can download metadata and the upload descriptions to the newly named table. But can we have Datahub understand renaming and do that automatically? Like if commands like *`ALTER TABLE table_name RENAME TO table_new_name`* were used, it should take descriptions and other documentation of table_name and assigne them to table_new_name?

If you do that and ingest on the new table, you should automatically get everything in. Manual will have to be ported over.

Which means that anything you added via the datahub ui will need to have their parent reassigned to the new dataset URN. Which is what we talked about yesterday with python querying and changing every key aspect

Could you please elaborate on python querying and changing key aspects? Like list the steps for me

<@U03LYB2ESJ0> you could either do this programmatically using the python emitter/REST emitter <https://datahubproject.io/docs/metadata-ingestion/as-a-library/>, but you’d need to know the URNS for everything

<@U03LYB2ESJ0>, I believe that the key question is whether DataHub can know that somebody renamed the table using the alter table command. I don't think that DataHub processes database logs, thus no "automated" remapping/renaming seems to be feasible from my point of view. You can do that by performing updates as suggested by <@U042KCFV9GX> above, but it wouldn't be automatic - as already mentioned by Paul, you need to know which original dataset (URN) was renamed to which new name and perform the updates accordingly.