-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Don't set max_execution_time for MySQL 5.6 #22097
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
base: master
Are you sure you want to change the base?
Don't set max_execution_time for MySQL 5.6 #22097
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files🚀 New features to boost your workflow:
|
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected * Fix with Cursor requires Datadog plugin ≥v2.17.0 🔗 Commit SHA: bf5b173 | Docs | Datadog PR Page | Was this helpful? Give us feedback! |
| with closing(self._check._mysql_metadata.get_db_connection().cursor(CommenterDictCursor)) as cursor: | ||
| query = self._get_tables_query() | ||
| max_execution_time = self._config.max_execution_time | ||
| if self._check.is_mariadb: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For completeness can we add a version check for mariadb here as well. MAX_STATEMENT_TIME was added in 10.1.1 which is also quite old, but better to guard against potential issues here
What does this PR do?
Skips setting the
max_execution_timewhen collecting schemas for MySQL 5.6.Motivation
max_execution_timeis not supported in MySQL 5.6.Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged