planner, executor: add PARAMS column to the output of show traffic jobs

[djshow832]

What problem does this PR solve?

Issue Number: close #59871

Problem Summary:
The only way to see the parameters is to check tiproxy logs, which is unfriendly.

What changed and how does it work?

Add an extra column PARAMS to the output of show traffic jobs

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.

mysql> show traffic jobs;
+----------------------------+----------------------------+----------------+---------+----------+--------+-------------+----------------------------------------------------------------------------+
| START_TIME                 | END_TIME                   | INSTANCE       | TYPE    | PROGRESS | STATUS | FAIL_REASON | PARAMS                                                                     |
+----------------------------+----------------------------+----------------+---------+----------+--------+-------------+----------------------------------------------------------------------------+
| 2025-03-03 18:53:09.000000 | 2025-03-03 18:53:10.000000 | 127.0.0.1:3080 | replay  | 0%       | done   |             | INPUT="/tmp/traffic", USER="root", SPEED=0.000000, READ_ONLY=false         |
| 2025-03-03 18:52:58.000000 | 2025-03-03 18:53:08.000000 | 127.0.0.1:3080 | capture | 100%     | done   |             | OUTPUT="/tmp/traffic", DURATION="10s", COMPRESS=true, ENCRYPTION_METHOD="" |
+----------------------------+----------------------------+----------------+---------+----------+--------+-------------+----------------------------------------------------------------------------+
2 rows in set (0.02 sec)

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 @djshow832. 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.

Details

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.3549%. Comparing base (448649e) to head (07af943).
Report is 5 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59872        +/-   ##
================================================
+ Coverage   72.9395%   73.3549%   +0.4153%     
================================================
  Files          1699       1700         +1     
  Lines        469556     470721      +1165     
================================================
+ Hits         342492     345297      +2805     
+ Misses       105948     104384      -1564     
+ Partials      21116      21040        -76     

Flag	Coverage Δ
integration	42.8109% <22.2222%> (?)
unit	72.2156% <100.0000%> (+0.0671%)	⬆️

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	44.3663% <ø> (-0.5793%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: AilinKid, xhebox

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:

• OWNERS [AilinKid,xhebox]
• pkg/planner/OWNERS [AilinKid]

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:

• 2025-03-03 13:33:02.13379037 +0000 UTC m=+275695.262710115: ☑️ agreed by xhebox.
• 2025-03-04 06:32:59.891943095 +0000 UTC m=+336893.020862839: ☑️ agreed by AilinKid.

[djshow832]

/retest

[tiprow]

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

Details

In response to this:

/retest

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.

[djshow832]

/ok-to-test

[djshow832]

/retest