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.

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

feat(ingest): track thread count in ingestion report #9566

Merged
merged 1 commit into from Jan 4, 2024
Merged

feat(ingest): track thread count in ingestion report #9566

merged 1 commit into from Jan 4, 2024

Conversation

hsheth2
Copy link
Collaborator

@hsheth2 hsheth2 commented Jan 4, 2024

Checklist

  • The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
  • Links to related issues (if applicable)
  • Tests for the changes have been added/updated (if applicable)
  • Docs related to the changes have been added/updated (if applicable). If a new feature has been added a Usage Guide has been added for the same.
  • For any breaking change/potential downtime/deprecation/big changes an entry has been made in Updating DataHub

@github-actions github-actions bot added ingestion PR or Issue related to the ingestion of metadata datahub-community-champion PRs authored by DataHub Community Champions labels Jan 4, 2024
@hsheth2
Copy link
Collaborator Author

hsheth2 commented Jan 4, 2024

CI failures are unrelated (and possibly related to #9549)

@hsheth2 hsheth2 merged commit 2268c0c into datahub-project:master Jan 4, 2024
52 of 54 checks passed
@hsheth2 hsheth2 deleted the pipeline-thread-count branch January 4, 2024 21:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@asikowitz asikowitz asikowitz approved these changes

Assignees
No one assigned
Labels
datahub-community-champion PRs authored by DataHub Community Champions ingestion PR or Issue related to the ingestion of metadata
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@hsheth2 @asikowitz