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

DataHub

In the lineage docs (<https://datahubproject.io/docs/lineage/sample_code>) why is a `MetadataChangeProposalWrapper` preferable over `MetadataChangeEvent`?

<@U02GSKURF33>: the `MetadataChangeEvent` is a large monolithic class with a lot of union aspects inlined into it. We are moving away from that model for newer aspects.  So to future proof your code, would recommend working with the `MetadataChangeProposalWrapper` class

here is how the newer events are modeled on the server side (<https://datahubproject.io/docs/advanced/mcp-mcl/>)

sounds like this recommendation to use MCPW also applies for other ingestion (ex. dataset), not just for lineage?

we are going through the ingestion sources and changing them slowly over time

and the new spark lineage PR that recently landed uses MCPW exclusively for example.

cool, i'll take a look at that. Thanks for getting back to me so quick :slightly_smiling_face: