Skip to content

statistics: refine comments to FMSketch#53601

Merged
ti-chi-bot[bot] merged 4 commits intopingcap:masterfrom
0xPoe:rustin-patch-fmsketch-comments
May 28, 2024
Merged

statistics: refine comments to FMSketch#53601
ti-chi-bot[bot] merged 4 commits intopingcap:masterfrom
0xPoe:rustin-patch-fmsketch-comments

Conversation

@0xPoe
Copy link
Member

@0xPoe 0xPoe commented May 28, 2024

What problem does this PR solve?

Issue Number: close None

Problem Summary:

What changed and how does it work?

I have made the necessary corrections to the comments for FMSketch. Although we refer to it as FMSketch, it is actually a variant of FMSketch. The concept is quite similar, but the implementation differs significantly. Therefore, we need to update the comment to avoid confusion.

Some more links:

  1. https://dsf.berkeley.edu/cs286/papers/synopses-fntdb2012.pdf (chapter 5.4.3)
  2. https://users.cs.utah.edu/~lifeifei/cs6931/lecture5 (page 3)
  3. https://www.vldb.org/conf/2001/P541.pdf (section 3.2)

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

Signed-off-by: hi-rustin <rustin.liu@gmail.com>
@0xPoe 0xPoe added the skip-issue-check Indicates that a PR no need to check linked issue. label May 28, 2024
@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels May 28, 2024
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
Copy link
Member Author

@0xPoe 0xPoe left a comment

Choose a reason for hiding this comment

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

🔢 Self-check (PR reviewed by myself and ready for feedback.)

Copy link
Contributor

@AilinKid AilinKid left a comment

Choose a reason for hiding this comment

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

LGGGGGTM

@0xPoe 0xPoe requested review from elsa0520 and time-and-fate May 28, 2024 03:43
@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels May 28, 2024
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
@codecov
Copy link

codecov bot commented May 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.8615%. Comparing base (57d0b40) to head (4866fcf).
Report is 9 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #53601        +/-   ##
================================================
+ Coverage   72.4916%   74.8615%   +2.3699%     
================================================
  Files          1506       1507         +1     
  Lines        430600     434617      +4017     
================================================
+ Hits         312149     325361     +13212     
+ Misses        99229      89253      -9976     
- Partials      19222      20003       +781     
Flag Coverage Δ
integration 49.7002% <66.6666%> (?)
unit 71.6425% <100.0000%> (+0.1708%) ⬆️

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

Components Coverage Δ
dumpling 53.9957% <ø> (ø)
parser ∅ <ø> (∅)
br 50.5286% <ø> (+9.1279%) ⬆️

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

ti-chi-bot bot commented May 28, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-05-28 03:43:16.802068684 +0000 UTC m=+2747950.559204258: ☑️ agreed by AilinKid.
  • 2024-05-28 03:59:05.81397254 +0000 UTC m=+2748899.571108107: ☑️ agreed by hawkingrei.

@hawkingrei
Copy link
Member

/ok-to-test

@ti-chi-bot ti-chi-bot bot added the ok-to-test Indicates a PR is ready to be tested. label May 28, 2024
@time-and-fate
Copy link
Member

/hold

@ti-chi-bot ti-chi-bot bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 28, 2024
Signed-off-by: hi-rustin <rustin.liu@gmail.com>
@0xPoe 0xPoe force-pushed the rustin-patch-fmsketch-comments branch from 704fc58 to 4866fcf Compare May 28, 2024 06:07
@0xPoe 0xPoe requested a review from time-and-fate May 28, 2024 06:07
@hawkingrei
Copy link
Member

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label May 28, 2024
Copy link
Contributor

@elsa0520 elsa0520 left a comment

Choose a reason for hiding this comment

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

LGTM

@ti-chi-bot
Copy link

ti-chi-bot bot commented May 28, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, 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

Details 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

@0xPoe
Copy link
Member Author

0xPoe commented May 28, 2024

/retest

@0xPoe
Copy link
Member Author

0xPoe commented May 28, 2024

/retest

@ti-chi-bot ti-chi-bot bot merged commit 772db20 into pingcap:master May 28, 2024
@0xPoe 0xPoe deleted the rustin-patch-fmsketch-comments branch May 28, 2024 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved lgtm ok-to-test Indicates a PR is ready to be tested. release-note-none Denotes a PR that doesn't merit a release note. sig/planner SIG: Planner size/M Denotes a PR that changes 30-99 lines, ignoring generated files. skip-issue-check Indicates that a PR no need to check linked issue.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants