Skip to content

Clarification on Documentation Propagation #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Clarification on Documentation Propagation #80

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/automations/docs-propagation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -125,4 +125,15 @@ used to propagate the description.

<p align="left">
<img width="50%" src="https://raw.githubusercontent.com/datahub-project/static-assets/main/imgs/automation/oss/docs-propagation/view-propagated-docs.png"/>
</p>
</p>

## Troubleshooting Documentation Propagation Issues

If you encounter issues with documentation propagation, consider the following steps:

1. **Verify Propagation Settings**: Ensure that the feature is enabled as described above.
2. **Check Lineage Configuration**: Use the DataHub UI to verify column-level lineage connections.
3. **Review Ingestion Logs**: Check logs for any errors or warnings related to metadata propagation.
4. **Manual Verification**: Inspect the DataHub UI or use the DataHub Python SDK to verify column descriptions.

For more advanced scenarios, consider reviewing the source code or using the action framework for custom propagation logic.