Skip to content
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

[DOP-22366] Basic column lineage handling in consumer #155

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

dolfinus
Copy link
Member

@dolfinus dolfinus commented Feb 4, 2025

Change Summary

Depends on #153.

Implement basic column lineage handler in consumer.

There are 2 DTO classes:

  • ColumnLineageDTO - describes tuple (operation, source_dataset, target_dataset).
  • DatasetColumnRelationDTO - describes source_column -> target_column (optional) relations within ColumnLineageDTO

Extractor builds list of these ColumnLineageDTO for each operation, and then perform bulk insert. Table rows are immutable, using ON CONFLICT DO NOTHING with few additional checks to reduce database IO.

This lacks any tests, these should be added in next commits.

Related issue number

Checklist

  • Commit message and PR title is comprehensive
  • Keep the change as small as possible
  • Unit and integration tests for the changes exist
  • Tests pass on CI and coverage does not decrease
  • Documentation reflects the changes where applicable
  • docs/changelog/next_release/<pull request or issue id>.<change type>.rst file added describing change
    (see CONTRIBUTING.rst for details.)
  • My PR is ready to review.

@dolfinus dolfinus requested a review from TiGrib February 4, 2025 11:41
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.

1 participant