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

Fix for schema tracker not recognizing RENAME for schema reloading #8963

Merged
merged 2 commits into from
Oct 18, 2021

Conversation

aquarapid
Copy link
Contributor

See #8960

Need to still think if there are other cases we should add tests for.

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
Signed-off-by: Jacques Grove <aquarapid@gmail.com>
@aquarapid aquarapid changed the title Quick fix for schema tracker not recognizing RENAME for schema reloading Fix for schema tracker not recognizing RENAME for schema reloading Oct 11, 2021
@aquarapid aquarapid requested a review from sougou October 11, 2021 20:14
@aquarapid aquarapid marked this pull request as ready for review October 11, 2021 20:14
Copy link
Contributor

@sougou sougou left a comment

Choose a reason for hiding this comment

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

We should also have @systay or @harshit-gangal eyeball this.

@harshit-gangal
Copy link
Member

@sougou This is not related to vtgate schema tracker, this is related to vreplication schema versioning :)

@5antelope
Copy link
Member

gentle nudge, it would be great if we can land this so we can try it out :-)

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.

6 participants