Skip to content

POC: _vt schema initialization on tablet init using declarative schemas#11235

Closed
rohit-nayak-ps wants to merge 10 commits intovitessio:mainfrom
planetscale:declarative-vt-schema
Closed

POC: _vt schema initialization on tablet init using declarative schemas#11235
rohit-nayak-ps wants to merge 10 commits intovitessio:mainfrom
planetscale:declarative-vt-schema

Conversation

@rohit-nayak-ps
Copy link
Copy Markdown
Member

Description

This PR is an attempt to use our schemadiff library to declare the desired _vt schema as of the current Vitess main. On tablet init then we use schemadiff to calculate the required alters based on the current _vt schema and reach the desired schema.

If this works well we can avoid using withddl altogether.

There is an experimental vttablet flag --init-vt-schema-on-tablet-init that has been introduced which can be used to trigger this functionality. For now this POC defaults the flag to true so that all tests will run in CI with this feature.

The unit_tests now run. Some tests that specifically depend on the old functionality (either withddl or other schema creation logic) needed to be skipped/modified based on the flag.

There are a few points now which invoke the sidecardb.Init():

  • In mysqlctl.PopulateMetadataTables() which is a common entry point when a tablet comes up with or without backup/restore.
  • In rpc_replication.InitPrimary() because there were calls directly to this function which seemed to bypass the previous step: need to investigate this more
  • In healthstreamer.InitSchemaLocked: this was added only to pass vttestserver.TestForeignKeysAndDDLModes. Need to investigate this more

Related Issue(s)

#10133

Checklist

  • "Backport me!" label has been added if this change should be backported
  • Tests were added or are not required
  • Documentation was added or is not required

@vitess-bot
Copy link
Copy Markdown
Contributor

vitess-bot bot commented Sep 15, 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, review whether it is really needed. The flag names should be clear and intuitive (as far as possible), and the flag's help should be descriptive. Additionally, flag names should use dashes (-) as word separators rather than underscores (_).
  • If a workflow is added or modified, each items in Jobs should be named in order to mark it as required. If the workflow should be required, the GitHub Admin should be notified.

Bug fixes

  • There should be at least one unit or end-to-end test.
  • The Pull Request description should either include a link to an issue that describes the bug OR an actual description of the bug and how to reproduce, along with a description of the fix.

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.

@rohit-nayak-ps rohit-nayak-ps added Type: Feature Type: Enhancement Logical improvement (somewhere between a bug and feature) Component: General Changes throughout the code base and removed Type: Feature labels Sep 16, 2022
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
…ed prs issue

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
…gs for it

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
… otherwise. Use 'create table if not exists'

Signed-off-by: Rohit Nayak <rohit@planetscale.com>
Signed-off-by: Rohit Nayak <rohit@planetscale.com>
@rohit-nayak-ps
Copy link
Copy Markdown
Member Author

Closing in favor of #11520

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

Labels

Component: General Changes throughout the code base Do Not Merge Type: Enhancement Logical improvement (somewhere between a bug and feature)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant