Skip to content

[release-19.0] vtexplain: Fix setting up the column information (#15275)#15282

Merged
dbussink merged 1 commit intorelease-19.0from
backport-15275-to-release-19.0
Feb 19, 2024
Merged

[release-19.0] vtexplain: Fix setting up the column information (#15275)#15282
dbussink merged 1 commit intorelease-19.0from
backport-15275-to-release-19.0

Conversation

@vitess-bot
Copy link
Contributor

@vitess-bot vitess-bot bot commented Feb 19, 2024

Description

This is a backport of #15275

Signed-off-by: Dirkjan Bussink <d.bussink@gmail.com>
@vitess-bot vitess-bot bot added the Backport This is a backport label Feb 19, 2024
@vitess-bot vitess-bot bot requested a review from systay as a code owner February 19, 2024 10:24
@vitess-bot vitess-bot bot added Component: vtexplain changes made to vtexplain code Type: Bug labels Feb 19, 2024
@vitess-bot
Copy link
Contributor Author

vitess-bot bot commented Feb 19, 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.

@github-actions github-actions bot added this to the v19.0.0 milestone Feb 19, 2024
@codecov
Copy link

codecov bot commented Feb 19, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (b352323) 67.29% compared to head (6f044e2) 67.30%.

Additional details and impacted files
@@              Coverage Diff              @@
##           release-19.0   #15282   +/-   ##
=============================================
  Coverage         67.29%   67.30%           
=============================================
  Files              1558     1558           
  Lines            192072   192068    -4     
=============================================
+ Hits             129261   129270    +9     
+ Misses            62811    62798   -13     

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

@dbussink dbussink merged commit 7f6222e into release-19.0 Feb 19, 2024
@dbussink dbussink deleted the backport-15275-to-release-19.0 branch February 19, 2024 13:45
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: vtexplain changes made to vtexplain code Type: Bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants