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

Backport: Backups: Support InnoDB Redo Log Location With 8.0.30+ #10895

Merged
merged 4 commits into from
Aug 2, 2022

Conversation

mattlord
Copy link
Contributor

@mattlord mattlord commented Jul 31, 2022

Description

This is a backport of #10847.

Related Issue(s)

Checklist

deepthi and others added 2 commits July 31, 2022 09:24
…kups

... removing the temporary workflow changes on main

Backups: Support InnoDB Redo Log Location With 8.0.30+
Signed-off-by: Matt Lord <mattalord@gmail.com>
WARN [linters context] structcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the golangci/golangci-lint#2649.
go/mysql/conn_flaky_test.go:658:2: S1001: should use copy() instead of a loop (gosimple)
	for j, i := range t.queryPacket {
	^

Signed-off-by: Matt Lord <mattalord@gmail.com>
@vitess-bot
Copy link
Contributor

vitess-bot bot commented Jul 31, 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.
  • 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.

@mattlord mattlord added Component: Backup and Restore Type: Bug Type: Enhancement Logical improvement (somewhere between a bug and feature) labels Jul 31, 2022
@mattlord mattlord marked this pull request as ready for review July 31, 2022 13:40
@mattlord mattlord requested review from GuptaManan100 and rsajwani and removed request for systay, harshit-gangal and rohit-nayak-ps July 31, 2022 13:41
mattlord added a commit to planetscale/vitess that referenced this pull request Jul 31, 2022
This should not be merged until after the backport is merged:
  vitessio#10895

Signed-off-by: Matt Lord <mattalord@gmail.com>
This is needed as we do not currently plan on backporting the backup
fixes to v13 and older, thus release-13.0 will not ever get the
backup fixes to support 8.0.30+.

If we do decide to backport the fixes to release-13.0 then this
workflow change can be reverted.

Signed-off-by: Matt Lord <mattalord@gmail.com>
mattlord added a commit that referenced this pull request Aug 1, 2022
This should not be merged until after the backport is merged:
  #10895

Signed-off-by: Matt Lord <mattalord@gmail.com>
@mattlord mattlord requested a review from frouioui as a code owner August 1, 2022 17:25
Signed-off-by: Matt Lord <mattalord@gmail.com>
@mattlord mattlord merged commit d5256b0 into vitessio:release-14.0 Aug 2, 2022
@mattlord mattlord deleted the backport-10847 branch August 2, 2022 14:10
@mattlord mattlord added the Backport This is a backport label Aug 2, 2022
systay pushed a commit to planetscale/vitess that referenced this pull request Aug 19, 2022
…essio#10895) (vitessio#911)

Backups: Support InnoDB Redo Log Location With 8.0.30+
Signed-off-by: Matt Lord <mattalord@gmail.com>

* Address linter warning:

WARN [linters context] structcheck is disabled because of go1.18. You can track the evolution of the go1.18 support by following the golangci/golangci-lint#2649.
go/mysql/conn_flaky_test.go:658:2: S1001: should use copy() instead of a loop (gosimple)
	for j, i := range t.queryPacket {
	^

Signed-off-by: Matt Lord <mattalord@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backport This is a backport Component: Backup and Restore Type: Bug Type: Enhancement Logical improvement (somewhere between a bug and feature)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants