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

planner: refactor infoschema predicate extractors #55502

Merged
merged 7 commits into from
Aug 21, 2024

Conversation

tangenta
Copy link
Contributor

@tangenta tangenta commented Aug 19, 2024

What problem does this PR solve?

Issue Number: ref #50305

Problem Summary:

Previously, we have a few usages like ex.Filter("partition_name", pi.Name.L) which is easy to misuse.

What changed and how does it work?

  • Add HasXXX method for each extractors, remove Filters.
  • Extract similar code ListSchemasAndTables to InfoSchemaBaseExtractor.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added do-not-merge/needs-linked-issue do-not-merge/needs-tests-checked release-note-none Denotes a PR that doesn't merit a release note. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. sig/planner SIG: Planner labels Aug 19, 2024
Copy link

tiprow bot commented Aug 19, 2024

Hi @tangenta. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

Copy link

codecov bot commented Aug 19, 2024

Codecov Report

Attention: Patch coverage is 98.86792% with 3 lines in your changes missing coverage. Please review.

Project coverage is 75.1325%. Comparing base (7342d1d) to head (f8a458e).
Report is 29 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #55502        +/-   ##
================================================
+ Coverage   72.8872%   75.1325%   +2.2452%     
================================================
  Files          1576       1578         +2     
  Lines        440796     447705      +6909     
================================================
+ Hits         321284     336372     +15088     
+ Misses        99789      91058      -8731     
- Partials      19723      20275       +552     
Flag Coverage Δ
integration 49.6666% <95.4717%> (?)
unit 72.3026% <97.3584%> (+0.3537%) ⬆️

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

Components Coverage Δ
dumpling 52.9567% <ø> (ø)
parser ∅ <ø> (∅)
br 51.8821% <ø> (+5.8916%) ⬆️

@@ -1748,10 +1741,10 @@ func (e *memtableRetriever) setDataForMetricTables() {
e.rows = rows
}

func keyColumnUsageInTable(schema model.CIStr, table *model.TableInfo, extractor *plannercore.InfoSchemaKeyColumnUsageExtractor) [][]types.Datum {
func keyColumnUsageInTable(schema model.CIStr, table *model.TableInfo, ex *plannercore.InfoSchemaKeyColumnUsageExtractor) [][]types.Datum {
var rows [][]types.Datum
if table.PKIsHandle {
Copy link
Member

Choose a reason for hiding this comment

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

Merge L1746 and L1747

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@@ -1792,7 +1783,7 @@ func keyColumnUsageInTable(schema model.CIStr, table *model.TableInfo, extractor
continue
}

if extractor != nil && extractor.Filter("constraint_name", filterIdxName) {
if !ex.HasConstraint(filterIdxName) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This makes no difference.
People forge to write the extractor.Filter( ... they can also forget to write HasXXX?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Just trying to avoid using string literal here

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Aug 20, 2024
Copy link

ti-chi-bot bot commented Aug 21, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, tiancaiamao

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added approved lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Aug 21, 2024
Copy link

ti-chi-bot bot commented Aug 21, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-08-20 13:44:24.512197537 +0000 UTC m=+273059.646647660: ☑️ agreed by tiancaiamao.
  • 2024-08-21 05:22:14.770658669 +0000 UTC m=+329329.905108790: ☑️ agreed by hawkingrei.

@ti-chi-bot ti-chi-bot bot merged commit 99180a8 into pingcap:master Aug 21, 2024
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants