Skip to content

OnlineDDL/vitess fix: convert data type to JSON #10390

Merged
shlomi-noach merged 4 commits intovitessio:mainfrom
planetscale:online-ddl-vrepl-varchar-to-json
May 31, 2022
Merged

OnlineDDL/vitess fix: convert data type to JSON #10390
shlomi-noach merged 4 commits intovitessio:mainfrom
planetscale:online-ddl-vrepl-varchar-to-json

Conversation

@shlomi-noach
Copy link
Copy Markdown
Contributor

Description

This PR fixes vitess migrations where a column is modified from a non-JSON type into JSON. When converting to JSON, vreplication adds a convert(%v using utf8mb4) wrapper around the column. However, because in our scenario the original column is non-JSON, the wrapper is not added.

We now analyze the scenario where source column is non-JSON and target column is JSON, and ensure to add convert() around the column name.

Also, this PR now identifies a series of errors as non-recoverable, such that a vreplication stream will fail the moment it encounters them. The added errors are all JSON conversion -related (e.g. empty document, invalid JSON format, data too long, etc.)

vrepl_suite tests are added to cover multiple scenarios.

Related Issue(s)

#6926

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

Deployment Notes

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
…8mb4)'

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
@github-actions
Copy link
Copy Markdown
Contributor

Review Checklist

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

General

  • Ensure that the Pull Request has the correct release notes label. release notes none should only be used for PRs that are so trivial that they need not be 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.

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.

Copy link
Copy Markdown
Member

@rohit-nayak-ps rohit-nayak-ps left a comment

Choose a reason for hiding this comment

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

lgtm

The gh-ost test failed once and succeeded the second time, but as we have found the action still failed. Restarted it: we should keep an eye out since we have found recently that many of the flaky tests did have underlying bugs.

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