-
Notifications
You must be signed in to change notification settings - Fork 208
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
Conversation
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>
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this 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!
There was a problem hiding this 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.
--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) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
To be merged only once vitessio/vitess#14923 is merged. |
Signed-off-by: Shlomi Noach <2607934+shlomi-noach@users.noreply.github.com>
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 invtctl
andvtctldclient
docs.Replaces #1662 which was a mess.