Skip to content

Horizon planning on operators#12506

Merged
frouioui merged 2 commits intovitessio:mainfrom
planetscale:horizon-planning-on-operators
Mar 22, 2023
Merged

Horizon planning on operators#12506
frouioui merged 2 commits intovitessio:mainfrom
planetscale:horizon-planning-on-operators

Conversation

@frouioui
Copy link
Copy Markdown
Member

@frouioui frouioui commented Feb 28, 2023

Description

This PR moves more of the horizon planning to the operators.

Related Issue(s)

#11626

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Did the new or modified tests pass consistently locally and on the CI
  • Documentation was added or is not required

Deployment Notes

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@vitess-bot vitess-bot bot added NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says labels Feb 28, 2023
@vitess-bot
Copy link
Copy Markdown
Contributor

vitess-bot bot commented Feb 28, 2023

Review Checklist

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

General

  • Ensure that the Pull Request has a descriptive title.
  • If this is a change that users need to know about, please apply the release notes (needs details) label so that merging is blocked unless the summary release notes document is included.
  • If a test is added or modified, there should be a documentation on top of the test to explain what the expected behavior is what the test does.

If a new flag is being introduced:

  • Is it really necessary to add this flag?
  • Flag names should be clear and intuitive (as far as possible)
  • Help text should be descriptive.
  • Flag names should use dashes (-) as word separators rather than underscores (_).

If a workflow is added or modified:

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

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should include a link to an issue that describes the bug.

Non-trivial changes

  • There should be some code comments as to why things are implemented the way they are.

New/Existing features

  • Should be documented, either by modifying the existing documentation or creating new documentation.
  • New features should have a link to a feature request issue or an RFC that documents the use cases, corner cases and test cases.

Backward compatibility

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

@systay systay force-pushed the horizon-planning-on-operators branch from 5789768 to eda6c6f Compare February 28, 2023 10:35
@frouioui frouioui added Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: Query Serving and removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says labels Mar 15, 2023
@frouioui frouioui marked this pull request as ready for review March 15, 2023 16:01
@frouioui
Copy link
Copy Markdown
Member Author

frouioui commented Mar 16, 2023

Upgrade Downgrade test failures can safely be ignored here. They're due to this branch being old and not on go1.20.1.

Copy link
Copy Markdown
Member

@harshit-gangal harshit-gangal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good. Comments can be added for readability.

Signed-off-by: Florent Poinsard <florent.poinsard@outlook.fr>
@frouioui frouioui force-pushed the horizon-planning-on-operators branch from 96f5fe1 to 35d53e4 Compare March 22, 2023 07:30
@frouioui frouioui merged commit e75b9c8 into vitessio:main Mar 22, 2023
@frouioui frouioui deleted the horizon-planning-on-operators branch March 22, 2023 09:33
Comment on lines +67 to +69
canShortcut := isRoute && sel.Having == nil && !needsOrdering

// If we still have a HAVING clause, it's because it could not be pushed to the WHERE,
// so it probably has aggregations
switch {
case qp.NeedsAggregation() || sel.Having != nil:
return nil, rewrite.VisitChildren, errNotHorizonPlanned
case canShortcut && !needsOrdering && !qp.NeedsDistinct() && in.Select.GetLimit() == nil:
if !qp.NeedsAggregation() && sel.Having == nil && canShortcut && !needsOrdering && !qp.NeedsDistinct() && in.Select.GetLimit() == nil {
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

canShortcut is only used in the if condition which can be expanded as it will only add isRoute check rest of the checks are already present.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: Query Serving Type: Enhancement Logical improvement (somewhere between a bug and feature)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants