planner: Move the Selectivity function from the stats package into cardinality package

[qw4990]

What problem does this PR solve?

Issue Number: ref #46358

Problem Summary: Move the Selectivity function from the stats package into cardinality package

What is changed and how it works?

No logical change, just some code movement.

Follow with #46359

Move the Selectivity function from the stats package.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

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

[tiprow]

Hi @qw4990. 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/test-infra repository.

[qw4990]

This cycle import problem will be naturally resolved as we move more estimation functions from stats to cardinality package.

[elsa0520]

LGTM

[codecov]

Codecov Report

Merging #46405 (a473915) into master (3190885) will decrease coverage by 47.7582%.
Report is 2 commits behind head on master.
The diff coverage is 65.1351%.

Additional details and impacted files

@@                Coverage Diff                @@
##             master     #46405         +/-   ##
=================================================
- Coverage   73.4100%   25.6519%   -47.7582%     
=================================================
  Files          1292       1154        -138     
  Lines        393585     348750      -44835     
=================================================
- Hits         288931      89461     -199470     
- Misses        86282     248549     +162267     
+ Partials      18372      10740       -7632     

Flag	Coverage Δ
integration	25.6519% <65.1351%> (?)
unit	?

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

Components	Coverage Δ
dumpling	∅ <ø> (∅)
parser	∅ <ø> (∅)
br	0.1119% <ø> (-52.2465%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: elsa0520, hawkingrei, time-and-fate

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:

• OWNERS [hawkingrei,time-and-fate]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-08-24 11:02:40.339630339 +0000 UTC m=+1406524.888646310: ☑️ agreed by hawkingrei.
• 2023-08-24 11:48:42.256078576 +0000 UTC m=+1409286.805094563: ☑️ agreed by time-and-fate.

[qw4990]

/test unit-test

[tiprow]

@qw4990: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/test unit-test

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/test-infra repository.

[qw4990]

/ok-to-test

[qw4990]

/test tiprow_fast_test

[ti-chi-bot]

@qw4990: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test build
• /test canary-scan-security
• /test check-dev
• /test check-dev2
• /test mysql-test
• /test pingcap/tidb/canary_ghpr_unit_test
• /test pull-br-integration-test
• /test pull-common-test
• /test pull-e2e-test
• /test pull-integration-common-test
• /test pull-integration-copr-test
• /test pull-integration-ddl-test
• /test pull-integration-jdbc-test
• /test pull-integration-mysql-test
• /test pull-mysql-connector-test
• /test pull-sqllogic-test
• /test pull-tiflash-test
• /test unit-test

The following commands are available to trigger optional jobs:

• /test pull-notify-when-compatibility-sections-changed

Use /test all to run the following jobs that were automatically triggered:

• pingcap/tidb/ghpr_build
• pingcap/tidb/ghpr_check
• pingcap/tidb/ghpr_check2
• pingcap/tidb/ghpr_mysql_test
• pingcap/tidb/ghpr_unit_test

In response to this:

/test tiprow_fast_test

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/test-infra repository.