statistic: fix panic when building topN (#47928)

[ti-chi-bot]

This is an automated cherry-pick of #47928

Signed-off-by: hi-rustin rustin.liu@gmail.com

What problem does this PR solve?

Issue Number: close #35948

Problem Summary:

What is changed and how it works?

The issue arises when a value appears twice in the topN list, triggering a panic. The solution involves breaking out of the loop as soon as we find the duplicate value. This bug seems to occur only when the column is of JSON type. Since we haven't been able to reproduce the issue, we've added a warning log to print all topN values, helping us identify the duplicated value.

Check List

Tests

• Unit test
• Integration test
• We will test it on users env.
• 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.

Fixed a bug that caused a panic while generating the topN statistics

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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,qw4990]

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-10-30 10:13:24.580094476 +0000 UTC m=+2861602.167204621: ☑️ agreed by qw4990.
• 2023-10-30 10:15:45.262560146 +0000 UTC m=+2861742.849670291: ☑️ agreed by hawkingrei.