Skip to content

[release-20.0-rc] Handle Nullability for Columns from Outer Tables (#16174)#16186

Merged
systay merged 1 commit intorelease-20.0-rcfrom
backport-16174-to-release-20.0-rc
Jun 14, 2024
Merged

[release-20.0-rc] Handle Nullability for Columns from Outer Tables (#16174)#16186
systay merged 1 commit intorelease-20.0-rcfrom
backport-16174-to-release-20.0-rc

Conversation

@vitess-bot
Copy link
Copy Markdown
Contributor

@vitess-bot vitess-bot bot commented Jun 14, 2024

Description

This is a backport of #16174

Signed-off-by: Andres Taylor <andres@planetscale.com>
@vitess-bot
Copy link
Copy Markdown
Contributor Author

vitess-bot bot commented Jun 14, 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 v20.0.0 milestone Jun 14, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.50%. Comparing base (4865893) to head (9c28e79).

Additional details and impacted files
@@                 Coverage Diff                 @@
##           release-20.0-rc   #16186      +/-   ##
===================================================
+ Coverage            68.47%   68.50%   +0.02%     
===================================================
  Files                 1541     1541              
  Lines               197614   197625      +11     
===================================================
+ Hits                135314   135376      +62     
+ Misses               62300    62249      -51     

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

@shlomi-noach shlomi-noach mentioned this pull request Jun 14, 2024
34 tasks
@frouioui frouioui added the Release Blocker: release-20.0 This item blocks the release on branch release-20.0 label Jun 14, 2024
@systay systay merged commit c3c77e1 into release-20.0-rc Jun 14, 2024
@systay systay deleted the backport-16174-to-release-20.0-rc branch June 14, 2024 17:36
@frouioui frouioui removed the Release Blocker: release-20.0 This item blocks the release on branch release-20.0 label Jun 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants