-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
executor: filter on table_schema
for INFORMATION_SCHEMA.KEY_COLUMN_USAGE
table
#55162
Conversation
/check-issue-triage-complete |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #55162 +/- ##
================================================
+ Coverage 72.8356% 73.9979% +1.1622%
================================================
Files 1568 1568
Lines 439200 439203 +3
================================================
+ Hits 319894 325001 +5107
+ Misses 99604 94034 -5570
- Partials 19702 20168 +466
Flags with carried forward coverage won't be shown. Click here to find out more.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance6716, tangenta The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Signed-off-by: Yang Keao <[email protected]>
What problem does this PR solve?
Issue Number: close #55156
Problem Summary:
Previously, the condition
table_schema = ...
has no effect on tableINFORMATION_SCHEMA.KEY_COLUMN_USAGE
. This PR fixed it.What changed and how does it work?
Also filter on
table_schema
condition.Maybe I can add more automatically generated tests for
InfoSchemaTablesExtractor
🤔 later. We should verify that all these extracted columns work on all the information schema tables.Check List
Tests
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.