Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VReplication TableStreamer: Only stream tables in tablestreamer (ignore views) #14646

Merged

Conversation

rohit-nayak-ps
Copy link
Contributor

@rohit-nayak-ps rohit-nayak-ps commented Nov 30, 2023

Description

When we do an atomic copy the tablestreamer streams all tables. The corresponding MoveTables gets its own list of tables, for which it adds filters for each table as part of the vreplication stream's binlogsource. For non-atomic copy workflows, we stream each table in the binlogsource list of tables. On the target vreplication creates one table plan for each of these tables.

However we get a full list of tables again after we have taken a snapshot (after locking all tables) for atomic copy and stream those tables.

There was a bug where we were not excluding views from this list. Hence the target was seeing a stream from the view resulting in the target stream erroring out since it doesn't have this view in its list of table plans.

This PR fixes that bug. It also adds a view to the e2e test: that test fails without the fix in the PR.

Related Issue(s)

Fixes #14648

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

Copy link
Contributor

vitess-bot bot commented Nov 30, 2023

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.

@vitess-bot vitess-bot bot added NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsIssue A linked issue is missing for this Pull Request NeedsWebsiteDocsUpdate What it says labels Nov 30, 2023
@github-actions github-actions bot added this to the v19.0.0 milestone Nov 30, 2023
@rohit-nayak-ps rohit-nayak-ps removed NeedsDescriptionUpdate The description is not clear or comprehensive enough, and needs work NeedsWebsiteDocsUpdate What it says NeedsIssue A linked issue is missing for this Pull Request labels Nov 30, 2023
Signed-off-by: Rohit Nayak <[email protected]>
@rohit-nayak-ps rohit-nayak-ps marked this pull request as ready for review November 30, 2023 12:52
Copy link
Contributor

@mattlord mattlord left a comment

Choose a reason for hiding this comment

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

Just some minor suggestions. Thanks!

Comment on lines 125 to +126
tableName := row[0].ToString()
tableType := row[1].ToString()
Copy link
Contributor

Choose a reason for hiding this comment

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

I think that we should either switch to using named rows or add a quick len(row) check just to be sure we don't crash with index out of bounds in some odd cases.

Copy link
Contributor

@shlomi-noach shlomi-noach Nov 30, 2023

Choose a reason for hiding this comment

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

Named rows is a no-go here, because the column name is dynamically constructed by the schema name (e.g. Tables_in_mydb) which is a bit of a nightmare with UTF and escaping.

I'd say an output of SHOW FULL TABLES can be trusted to have two columns, much like SHOW VARIABLES can be trusted to have two columns.

At any case, if we choose to validate number of columns, we should return some outrageous error like Code_INTERNAL or something likewise dramatic.

go/vt/vttablet/tabletserver/vstreamer/tablestreamer.go Outdated Show resolved Hide resolved
@rohit-nayak-ps rohit-nayak-ps merged commit b28197b into vitessio:main Nov 30, 2023
116 checks passed
@rohit-nayak-ps rohit-nayak-ps deleted the atomic-copy-ignore-views-on-copy branch November 30, 2023 13:18
vitess-bot pushed a commit that referenced this pull request Nov 30, 2023
rohit-nayak-ps added a commit that referenced this pull request Nov 30, 2023
…estreamer (ignore views) (#14646) (#14649)

Signed-off-by: Rohit Nayak <[email protected]>
Co-authored-by: vitess-bot[bot] <108069721+vitess-bot[bot]@users.noreply.github.com>
Co-authored-by: Rohit Nayak <[email protected]>
ejortegau pushed a commit to slackhq/vitess that referenced this pull request Dec 13, 2023
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.

Atomic copy workflows fail for schemas with views
3 participants