Skip to content

refactoring: Horizon planning on the operators#11698

Closed
systay wants to merge 4 commits intovitessio:mainfrom
planetscale:operator-horizon
Closed

refactoring: Horizon planning on the operators#11698
systay wants to merge 4 commits intovitessio:mainfrom
planetscale:operator-horizon

Conversation

@systay
Copy link
Collaborator

@systay systay commented Nov 12, 2022

Description

Related Issue(s)

Checklist

  • "Backport to:" labels have been added if this change should be back-ported
  • Tests were added or are not required
  • Documentation was added or is not required

Deployment Notes

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

vitess-bot bot commented Nov 12, 2022

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 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.

Signed-off-by: Andres Taylor <andres@planetscale.com>
Comment on lines +121 to +136
r := newRoute(
&Update{
QTable: qt,
VTable: vindexTable,
Assignments: assignments,
ChangedVindexValues: cvv,
OwnedVindexQuery: ovq,
AST: updStmt,
},
RouteOpCode: opCode,
Keyspace: vindexTable.Keyspace,
VindexPreds: vp,
TargetDestination: dest,
}
opCode,
vindexTable.Keyspace,
dest,
vp,
nil,
nil,
)
Copy link
Member

Choose a reason for hiding this comment

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

Not a blocker at all, but just my personal opinion: It's quite unfortunate go does not support named arguments. The previous version that build the struct directly was much more readable, as you could see what the individual struct members were set to, where as now newRoute takes a bunch of values but it's not obvious what they mean (e.g. those two nil arguments at the end).

@github-actions
Copy link
Contributor

This PR is being marked as stale because it has been open for 30 days with no activity. To rectify, you may do any of the following:

  • Push additional commits to the associated branch.
  • Remove the stale label.
  • Add a comment indicating why it is not stale.

If no action is taken within 7 days, this PR will be closed.

@github-actions github-actions bot added the Stale Marks PRs as stale after a period of inactivity, which are then closed after a grace period. label Dec 15, 2022
@github-actions
Copy link
Contributor

This PR was closed because it has been stale for 7 days with no activity.

@github-actions github-actions bot closed this Dec 23, 2022
@frouioui frouioui mentioned this pull request Feb 28, 2023
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Component: Query Serving Stale Marks PRs as stale after a period of inactivity, which are then closed after a grace period. Type: Internal Cleanup

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants