Skip to content

Emitting Metadata for Containers and Datasets #86

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.

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 3 commits into
base: master
Choose a base branch
from

Conversation

runllm-pr-agent[bot]
Copy link

Changes Made

  • docs/architecture/metadata-ingestion.md
    • ## Push-based IntegrationAs long as... --> ## Push-based IntegrationAs long as...: The documentation currently lacks explicit guidance on how to emit metadata for both datasets and their containers using the MetadataChangeProposalWrapper in the DataHub Python SDK. Adding detailed instructions and examples on this process will provide clear, actionable guidance for users looking to programmatically update metadata for datasets and containers in DataHub.
  • docs/what/mxe.md
    • ### EmissionMCPs may be emitted by ... --> ### EmissionMCPs may be emitted by ...: The documentation needs to include guidance on emitting metadata for both datasets and containers using the MetadataChangeProposalWrapper in the DataHub Python SDK, as well as linking datasets to containers.
  • docs/api/datahub-apis.md
    • ## Python and Java SDKWe offer an S... --> ## Python and Java SDKWe offer an S...: The documentation should include guidance on emitting metadata for datasets and containers using the MetadataChangeProposalWrapper in the Python SDK, as this is a common use case for users managing metadata programmatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants