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

Adds additional debug logging to help with schema collection investigations #18754

Conversation

aldrickdev
Copy link
Contributor

What does this PR do?

This will add some debug logging for schema collection investigation

Motivation

Current difficulties with investigating schema collection issues

Review checklist (to be filled by reviewers)

  • Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
  • Changelog entries must be created for modifications to shipped code
  • Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
  • If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

lu-zhengda
lu-zhengda previously approved these changes Oct 2, 2024
Copy link

codecov bot commented Oct 2, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.81%. Comparing base (b6cbfdb) to head (a123015).
Report is 1 commits behind head on master.

Additional details and impacted files
Flag Coverage Δ
activemq ?
cassandra ?
hive ?
hivemq ?
ignite ?
jboss_wildfly ?
kafka ?
postgres 93.18% <100.00%> (+3.87%) ⬆️
presto ?
solr ?

Flags with carried forward coverage won't be shown. Click here to find out more.

@aldrickdev aldrickdev merged commit bdd7dc8 into master Oct 3, 2024
40 checks passed
@aldrickdev aldrickdev deleted the TDBM-61-Add-additional-debug-logging-to-help-with-Schema-Collection-investigations branch October 3, 2024 13:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants