master(dm): support extra SHOW FULL TABLES columns from PolarDB-X#12481
master(dm): support extra SHOW FULL TABLES columns from PolarDB-X#12481ti-chi-bot[bot] merged 4 commits intopingcap:masterfrom
Conversation
Summary of ChangesHello @GMHDBJD, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request undertakes a refactoring effort to enhance code consistency by relocating the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request refactors the code to use conn.GetTables instead of dbutil.GetTables, which is a good improvement for code organization. The implementation of the new conn.GetTables function is mostly correct, but I've suggested a couple of minor improvements for consistency and idiomatic Go.
A more critical issue is that the unit tests in dm/pkg/conn/db_test.go and dm/master/openapi_view_test.go appear to be broken by this change. They still mock the old SQL query from dbutil.GetTables (SHOW FULL TABLES ... WHERE ...). Please update the mocked queries to SHOW FULL TABLES IN ... without the WHERE clause to match the new implementation in conn.GetTables.
| if len(cols) < 2 { | ||
| return nil, errors.New("SHOW FULL TABLES returned less than 2 columns") | ||
| } |
There was a problem hiding this comment.
For consistency with the error handling in this package, it's better to return a terror error instead of a raw error created with errors.New. You can use terror.ErrDBUnExpect.Generate for this.
| if len(cols) < 2 { | |
| return nil, errors.New("SHOW FULL TABLES returned less than 2 columns") | |
| } | |
| if len(cols) < 2 { | |
| return nil, terror.ErrDBUnExpect.Generate("SHOW FULL TABLES returned less than 2 columns") | |
| } |
| var dummy interface{} | ||
| scanArgs[i] = &dummy |
There was a problem hiding this comment.
This loop for creating dummy scan arguments can be made more efficient and idiomatic. Instead of declaring a new dummy variable in each iteration, you can allocate space for the columns you want to ignore directly. Using sql.RawBytes is a good practice for this as it can avoid extra allocations.
| var dummy interface{} | |
| scanArgs[i] = &dummy | |
| scanArgs[i] = new(sql.RawBytes) |
Codecov Report❌ Patch coverage is Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. @@ Coverage Diff @@
## master #12481 +/- ##
===========================================
Coverage ? 53.3819%
===========================================
Files ? 1011
Lines ? 139905
Branches ? 0
===========================================
Hits ? 74684
Misses ? 59614
Partials ? 5607 🚀 New features to boost your workflow:
|
|
/retest |
| return tables, errors.Trace(rows.Err()) | ||
| } | ||
|
|
||
| func escapeName(name string) string { |
There was a problem hiding this comment.
Not related to this PR, but I found that there are three places in TiDB with this same (unexported) function 😂
|
@joechenrh: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
| } | ||
| defer baseDB.Close() | ||
| tableList, err := dbutil.GetTables(c.Request.Context(), baseDB.DB, schemaName) | ||
| tableList, err := conn.GetTables(c.Request.Context(), baseDB.DB, schemaName) |
There was a problem hiding this comment.
Could we add one 4-column regression for OpenAPIViewSuite.TestSourceAPI and one for the online-DDL checker path too? Right now the new coverage is mostly helper-level.
…20260325T091753Z # Conflicts: # sync_diff_inspector/source/source_test.go
OliverS929
left a comment
There was a problem hiding this comment.
LGTM overall. One small follow-up: please consider adding a test that actually enables config.OnlineDDLChecking or exercises OnlineDDLChecker.Check.
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Benjamin2037, joechenrh, OliverS929 The full list of commands accepted by this bot can be found here. The pull request process is described here |
[LGTM Timeline notifier]Timeline:
|
|
/retest |
What problem does this PR solve?
Issue Number: close #12569
What is changed and how it works?
conn.GetTableshelper for table discoverySHOW FULL TABLES ... WHERE Table_Type != 'VIEW'behavior for normal MySQL/TiDB resultsCheck List
Tests
go test ./dm/pkg/conn -run 'TestGetTables|TestFetchAllDoTables'go test ./dm/pkg/checker ./dm/master -run '^$'Questions
Will it cause performance regression or break compatibility?
No. Existing behavior for standard upstreams is kept unchanged. The parsing only becomes more permissive for extra result columns.
Do you need to update user documentation, design documentation or monitoring documentation?
No.
Release note