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

Docs: Backup/BackupShard --incremental-from-pos accepts backup name #1667

Merged
merged 4 commits into from
Jan 29, 2024

Conversation

shlomi-noach
Copy link
Contributor

This PR documents the changes in vitessio/vitess#14923, --incremental-from-pos accepting a backup name.

There is a lot of noise because of SHA signatures. The relevant changes are mostly in content/en/docs/19.0/user-guides/operating-vitess/backup-and-restore/creating-a-backup.md and otherwise in vtctl and vtctldclient docs.

Replaces #1662 which was a mess.

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

netlify bot commented Jan 24, 2024

Deploy Preview for vitess ready!

Name Link
🔨 Latest commit 6ea1589
🔍 Latest deploy log https://app.netlify.com/sites/vitess/deploys/65b7a67aabdc860008d9fa55
😎 Deploy Preview https://deploy-preview-1667--vitess.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@ajm188 ajm188 left a comment

Choose a reason for hiding this comment

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

thank you for your patience on this!

Copy link
Collaborator

@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.

Looks good! The only issue is the unrelated changes to the vtctldclient materialize command. I will see where that came from as I did not expect it.

Comment on lines +55 to +58
--mysql_server_version string Configure the MySQL version to use for example for the parser. (default "8.0.30-Vitess")
--source-keyspace string Keyspace where the tables queried in the 'source_expression' values within table-settings live.
--sql-max-length-errors int truncate queries in error logs to the given length (default unlimited)
--sql-max-length-ui int truncate queries in debug UIs to the given length (default 512) (default 512)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hmmm, this doesn't seem right.... I will see where this came from.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ah, I think it was parser related refactors that led to us getting these flags because we parse the query provided in the materialize statement. So this is fine.

@shlomi-noach
Copy link
Contributor Author

To be merged only once vitessio/vitess#14923 is merged.

Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
@shlomi-noach shlomi-noach merged commit baa4d3f into prod Jan 29, 2024
5 checks passed
@shlomi-noach shlomi-noach deleted the doc-incremental-from-backup-name branch January 29, 2024 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants