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

Remove unneeded loading of the MySQL driver #15502

Merged
merged 2 commits into from
Mar 18, 2024

Conversation

dbussink
Copy link
Contributor

These cases probably at some point actually used MySQL with Go's stdlib database/sql logic, but no longer do.

This is mostly testing logic except for vtorc. The initial code port from Orchestrator to vtorc likely kept the logic for a MySQL backend but we've long since only had vtorc using sqlite internally.

Checklist

  • "Backport to:" labels have been added if this change should be back-ported to release branches
  • If this change is to be back-ported to previous releases, a justification is included in the PR description
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on CI?
  • Documentation was added or is not required

These cases probably at some point actually used MySQL with Go's stdlib
`database/sql` logic, but no longer do.

This is mostly testing logic except for `vtorc`. The initial code port
from Orchestrator to `vtorc` likely kept the logic for a MySQL backend
but we've long since only had `vtorc` using `sqlite` internally.

Signed-off-by: Dirkjan Bussink <[email protected]>
Copy link
Contributor

vitess-bot bot commented Mar 17, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot added NeedsBackportReason If backport labels have been applied to a PR, a justification is required NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Mar 17, 2024
@dbussink dbussink removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request NeedsBackportReason If backport labels have been applied to a PR, a justification is required labels Mar 17, 2024
@github-actions github-actions bot added this to the v20.0.0 milestone Mar 17, 2024
Copy link

codecov bot commented Mar 17, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.66%. Comparing base (696fe0e) to head (56a749b).
Report is 117 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #15502      +/-   ##
==========================================
- Coverage   67.41%   65.66%   -1.76%     
==========================================
  Files        1560     1563       +3     
  Lines      192752   194474    +1722     
==========================================
- Hits       129952   127707    -2245     
- Misses      62800    66767    +3967     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Move loading the driver to where we also `sql.Open` the `sqlite` driver.
We don't need any generic logic and `GetGenericDB` is not called from
anywhere, so let's clean that up too.

Signed-off-by: Dirkjan Bussink <[email protected]>
@@ -28,6 +28,8 @@ import (
"sync"
"time"

_ "modernc.org/sqlite"
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Load it here since here is also where we do sql.Open.

Copy link
Member

@GuptaManan100 GuptaManan100 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@dbussink dbussink merged commit 4d4793d into vitessio:main Mar 18, 2024
102 checks passed
@dbussink dbussink deleted the cleanup-unneeded-mysql-driver-loads branch March 18, 2024 08:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component: VTorc Vitess Orchestrator integration Type: Internal Cleanup
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants