Skip to content

[release-20.0-rc] feat: add a LIMIT 1 on EXISTS subqueries to limit network overhead (#16153)#16192

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

[release-20.0-rc] feat: add a LIMIT 1 on EXISTS subqueries to limit network overhead (#16153)#16192
systay merged 1 commit intorelease-20.0-rcfrom
backport-16153-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 #16153

…16153)

Signed-off-by: Andres Taylor <andres@planetscale.com>
@vitess-bot vitess-bot bot requested a review from harshit-gangal as a code owner June 14, 2024 17:37
@vitess-bot vitess-bot bot requested a review from systay as a code owner June 14, 2024 17:37
@vitess-bot vitess-bot bot added Type: Enhancement Logical improvement (somewhere between a bug and feature) Type: Regression labels Jun 14, 2024
@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.

@frouioui frouioui mentioned this pull request Jun 14, 2024
34 tasks
@github-actions github-actions bot added this to the v20.0.0 milestone Jun 14, 2024
@frouioui frouioui added Release Blocker: release-20.0 This item blocks the release on branch release-20.0 and removed Release Blocker: release-20.0 This item blocks the release on branch release-20.0 labels Jun 14, 2024
@codecov
Copy link
Copy Markdown

codecov bot commented Jun 14, 2024

Codecov Report

Attention: Patch coverage is 70.58824% with 25 lines in your changes missing coverage. Please review.

Project coverage is 68.49%. Comparing base (4865893) to head (b25dcda).
Report is 2 commits behind head on release-20.0-rc.

Files Patch % Lines
.../vt/vtgate/planbuilder/operators/query_planning.go 67.53% 25 Missing ⚠️
Additional details and impacted files
@@                 Coverage Diff                 @@
##           release-20.0-rc   #16192      +/-   ##
===================================================
+ Coverage            68.47%   68.49%   +0.01%     
===================================================
  Files                 1541     1541              
  Lines               197614   197709      +95     
===================================================
+ Hits                135314   135411      +97     
+ Misses               62300    62298       -2     

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

@systay systay merged commit 6986d74 into release-20.0-rc Jun 15, 2024
@systay systay deleted the backport-16153-to-release-20.0-rc branch June 15, 2024 08:52
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: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature) Type: Regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants