Skip to content

[release-20.0] Add a note on QueryCacheHits and QueryCacheMisses in the release notes (#16299)#16306

Merged
frouioui merged 1 commit intorelease-20.0from
backport-16299-to-release-20.0
Jul 1, 2024
Merged

[release-20.0] Add a note on QueryCacheHits and QueryCacheMisses in the release notes (#16299)#16306
frouioui merged 1 commit intorelease-20.0from
backport-16299-to-release-20.0

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jul 1, 2024

Description

This is a backport of #16299

…notes (#16299)

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@vitess-bot vitess-bot bot added Backport This is a backport Component: Documentation docs related issues/PRs Component: Observability Pull requests that touch tracing/metrics/monitoring labels Jul 1, 2024
@vitess-bot vitess-bot bot requested a review from harshit-gangal as a code owner July 1, 2024 18:40
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jul 1, 2024

Review Checklist

Hello reviewers! 👋 Please follow this checklist when reviewing this Pull Request.

General

  • Ensure that the Pull Request has a descriptive title.
  • Ensure there is a link to an issue (except for internal cleanup and flaky test fixes), new features should have an RFC that documents use cases and test cases.

Tests

  • Bug fixes should have at least one unit or end-to-end test, enhancement and new features should have a sufficient number of tests.

Documentation

  • Apply the release notes (needs details) label if users need to know about this change.
  • New features should be documented.
  • There should be some code comments as to why things are implemented the way they are.
  • There should be a comment at the top of each new or modified test to explain what the test does.

New flags

  • Is this flag really necessary?
  • Flag names must be clear and intuitive, use dashes (-), and have a clear help text.

If a workflow is added or modified:

  • Each item in Jobs should be named in order to mark it as required.
  • If the workflow needs to be marked as required, the maintainer team must be notified.

Backward compatibility

  • Protobuf changes should be wire-compatible.
  • Changes to _vt tables and RPCs need to be backward compatible.
  • RPC changes should be compatible with vitess-operator
  • If a flag is removed, then it should also be removed from vitess-operator and arewefastyet, if used there.
  • vtctl command output order should be stable and awk-able.

@vitess-bot vitess-bot bot requested review from frouioui and timvaillancourt July 1, 2024 18:40
@github-actions github-actions bot added this to the v20.0.1 milestone Jul 1, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jul 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.65%. Comparing base (3335bea) to head (fdbcf0b).

Additional details and impacted files
@@               Coverage Diff                @@
##           release-20.0   #16306      +/-   ##
================================================
- Coverage         68.66%   68.65%   -0.01%     
================================================
  Files              1541     1541              
  Lines            197817   197817              
================================================
- Hits             135827   135821       -6     
- Misses            61990    61996       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@frouioui frouioui merged commit f9e613f into release-20.0 Jul 1, 2024
@frouioui frouioui deleted the backport-16299-to-release-20.0 branch July 1, 2024 19:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Backport This is a backport Component: Documentation docs related issues/PRs Component: Observability Pull requests that touch tracing/metrics/monitoring Type: Internal Cleanup

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant