Skip to content

feat: support table/column lineage for mysql backend #2077

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

Merged
merged 3 commits into from
Jan 12, 2023

Conversation

xuan616
Copy link
Member

@xuan616 xuan616 commented Jan 8, 2023

Summary of Changes

The change is related to issue #2072. It is about supporting table/column lineage for mysql backend end to end.

  • databuilder: updated table_lineage model for table/column lineage record iterator and the corresponding sample_data_loader_mysql.py
  • metadata_service: updated mysql_proxy.py to add lineage related endpoint.

Tests

Added unit tests in both databuilder and metadata_service for lineage related change.

Documentation

N/A

CheckList

Make sure you have checked all steps below to ensure a timely review.

  • PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"
  • PR includes a summary of changes.
  • PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
  • In case of new functionality, my PR adds documentation that describes how to use it.
    • All the public functions and the classes in the PR contain docstrings that explain what it does

@feng-tao
Copy link
Member

thanks @xuan616

@feng-tao feng-tao merged commit 251d4e7 into amundsen-io:main Jan 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:databuilder From databuilder folder area:metadata From the metadata folder
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants