From dfdbf8f1adf25636e078cbe21d4705e6bc6221ef Mon Sep 17 00:00:00 2001 From: runllm Date: Fri, 18 Apr 2025 11:09:07 +0000 Subject: [PATCH 1/2] Update docs-propagation.md --- docs/automations/docs-propagation.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/docs/automations/docs-propagation.md b/docs/automations/docs-propagation.md index e8eba08d3640e8..2f793943f3afb0 100644 --- a/docs/automations/docs-propagation.md +++ b/docs/automations/docs-propagation.md @@ -95,6 +95,26 @@ and then click "Initialize". This one-time step will kick off the back-filling process for existing descriptions. If you only want to begin propagating descriptions going forward, you can skip this step. +## Troubleshooting Column Description Propagation + +### Verification of Propagation Settings +Ensure that column-level documentation propagation is enabled. In Open Source DataHub, this feature is enabled by default. Navigate to 'Settings' > 'Features' to verify. + +### Lineage Configuration Checks +Ensure that the lineage between columns is correctly configured for propagation. Verify that the lineage between the source and target columns is established. + +### Ingestion Log Review +Review ingestion logs for any errors or warnings related to documentation propagation. This can provide insights into potential issues. + +### Manual Verification of Column Descriptions +Manually verify that the column descriptions are correctly set before propagation. Ensure that the source column has the correct description. + +### DataHub Version Compatibility +Check the DataHub version for feature support and compatibility. Ensure you are using a version that supports column description propagation. + +### Known Issues +Refer to the DataHub GitHub repository or community forums for known issues or bugs related to column description propagation. + ## Rolling Back Propagated Descriptions (DataHub Cloud Only) In DataHub Cloud, you can rollback all descriptions that have been propagated historically. From 61573fda59976a0024307675d36a15ce6d3246af Mon Sep 17 00:00:00 2001 From: runllm Date: Fri, 18 Apr 2025 11:09:07 +0000 Subject: [PATCH 2/2] Update lineage.md --- docs/api/tutorials/lineage.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/api/tutorials/lineage.md b/docs/api/tutorials/lineage.md index daa8f548b2360f..8f8280c4582dd9 100644 --- a/docs/api/tutorials/lineage.md +++ b/docs/api/tutorials/lineage.md @@ -131,6 +131,15 @@ You can now see the lineage between `fct_users_deleted` and `logging_events`. +### Troubleshooting Column Description Propagation + +- **Verification of Propagation Settings**: Ensure that column-level documentation propagation is enabled in your DataHub settings. +- **Lineage Configuration Checks**: Verify that the lineage between columns is correctly configured for propagation. +- **Ingestion Log Review**: Review ingestion logs for errors or warnings related to documentation propagation. +- **Manual Verification of Column Descriptions**: Check that the column descriptions are correctly set before propagation. +- **DataHub Version Compatibility**: Confirm that your DataHub version supports the feature and is compatible. +- **Known Issues**: Refer to the DataHub GitHub repository or community forums for known issues or bugs related to column description propagation. + ### Expected Outcome You can now see the column-level lineage between datasets. Note that you have to enable `Show Columns` to be able to see the column-level lineage.