workload-based learning: save the metrics and create new workload_values table#59126
workload-based learning: save the metrics and create new workload_values table#59126ti-chi-bot[bot] merged 11 commits intopingcap:masterfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
Hi @elsa0520. Thanks for your PR. PRs from untrusted users cannot be marked as trusted with I understand the commands that are listed here. DetailsInstructions 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. |
fa51440 to
ebe1657
Compare
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #59126 +/- ##
================================================
+ Coverage 72.9996% 74.9220% +1.9224%
================================================
Files 1693 1743 +50
Lines 468156 482488 +14332
================================================
+ Hits 341752 361490 +19738
+ Misses 105370 98413 -6957
- Partials 21034 22585 +1551
Flags with carried forward coverage won't be shown. Click here to find out more.
|
|
/test unit-test |
|
@elsa0520: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
General comments:
|
Oh, I just want to add the unit test after I finish the new system table of producer part. Because It is also another workload_jobs table will be raise in the next PR. So I didn't add the unit test in this PR |
OK, I will change it to workloadLearning |
89ffe40 to
b41c17f
Compare
I think it is still good to add unit tests incrementally. |
ghazalfamilyusa
left a comment
There was a problem hiding this comment.
Remaining issues:
- Remove comments not related to the PR
- Add a unit test incrementally
[LGTM Timeline notifier]Timeline:
|
|
/test pull-lightning-integration-test |
|
@elsa0520: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
/test pull-lightning-integration-test |
|
@elsa0520: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
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. |
|
/ok-to-test |
|
/approve |
pkg/session/bootstrap.go
Outdated
| primary key(module, name));` | ||
|
|
||
| // CreateWorkloadValuesTable is a table to store workload-based learning values for tidb. | ||
| CreateWorkloadValuesTable = `CREATE TABLE IF NOT EXISTS mysql.workload_values ( |
There was a problem hiding this comment.
Is there a standard naming convention that we use for these new tables that are TiDB extensions? I see many other cases of these, non-MySQL, tables where we prefix the table name with tidb_, pd_, tikv_ or similar across the mysql and performance_schema schemas.
I am concerned that this kind of unprefixed table name could lead to future conflicts and compatibility issues if MySQL introduces this table name in the future.
There was a problem hiding this comment.
Has been changed to tidb_workload_values
|
/test pull-lightning-integration-test |
|
/test pull-br-integration-test |
|
@elsa0520: The specified target(s) for
Use DetailsIn response to this:
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. |
|
@elsa0520: The specified target(s) for
Use DetailsIn response to this:
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. |
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AilinKid, benmeadowcroft, D3Hunter, ghazalfamilyusa, qw4990, wjhuang2016, XuHuaiyu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
What problem does this PR solve?
Issue Number: ref #58131
Problem Summary:
What changed and how does it work?
This PR implement the part of producer table cost feature:
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.