Skip to content

feat(ingest/fivetran): make ingestion limits configurable #15457

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

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

feat(ingest/fivetran): make ingestion limits configurable #15457

sgomezvillamor wants to merge 1 commit into from

Conversation

@sgomezvillamor
Copy link
Contributor

@sgomezvillamor sgomezvillamor commented Dec 1, 2025

Makes Fivetran ingestion limits configurable to allow controlled increase when needed.

Summary

  • Added configurable limits to FivetranLogConfig: max_jobs_per_connector, max_table_lineage_per_connector, max_column_lineage_per_connector
  • Default values remain the same (500, 120, 1000 respectively)
  • Added validation to ensure positive values
  • Updated documentation with configuration examples
  • Added comprehensive unit tests

Checklist

  • Tests added
  • Documentation updated

@github-actions github-actions bot added the ingestion PR or Issue related to the ingestion of metadata label Dec 1, 2025
@datahub-cyborg datahub-cyborg bot added the needs-review Label for PRs that need review from a maintainer. label Dec 1, 2025
@codecov
Copy link

codecov bot commented Dec 1, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

ingestion PR or Issue related to the ingestion of metadata needs-review Label for PRs that need review from a maintainer.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@sgomezvillamor