From 54db1c3dfe8ea25927562d1efffbaef6f9c6a872 Mon Sep 17 00:00:00 2001 From: bengotow Date: Sun, 17 Mar 2024 09:55:48 -0500 Subject: [PATCH] Add comment --- .../src/assets/lineage/useColumnLineageDataForAssets.tsx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/js_modules/dagster-ui/packages/ui-core/src/assets/lineage/useColumnLineageDataForAssets.tsx b/js_modules/dagster-ui/packages/ui-core/src/assets/lineage/useColumnLineageDataForAssets.tsx index e84d6f788c80f..65b36d755410b 100644 --- a/js_modules/dagster-ui/packages/ui-core/src/assets/lineage/useColumnLineageDataForAssets.tsx +++ b/js_modules/dagster-ui/packages/ui-core/src/assets/lineage/useColumnLineageDataForAssets.tsx @@ -33,6 +33,12 @@ export type AssetColumnLineageLocal = { export type AssetColumnLineages = {[graphId: string]: AssetColumnLineageLocal | undefined}; +/** + * The column definitions and the column lineage are in two separate metadata entries, + * and the definitions may be specified in definition-time or materialization-time metadata. + * Parse them both and combine the results into a single representation of asset columns + * that is easier for the rest of the front-end to use. + */ const getColumnLineage = ( asset: AssetColumnLineageQuery['assetNodes'][0], ): AssetColumnLineageLocal | undefined => {