Docs: preliminary notice about upcoming changes to lifecycle table names #1661
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Shlomi Noach <[email protected]>
4 tasks
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Preview of specific changed page: https://deploy-preview-1661--vitess.netlify.app/docs/19.0/user-guides/schema-changes/table-lifecycle/ |
mattlord
approved these changes
Jan 17, 2024
| @@ -80,6 +80,17 @@ Vitess does not track the state of the table lifecycle. The process is stateless | |||
| - The table `_vt_EVAC_6ace8bcef73211ea87e9f875a4d24e90_20210918093000` is held until `2021-09-18 09:30:00` | |||
| - The table `_vt_DROP_6ace8bcef73211ea87e9f875a4d24e90_20210921170000` is eligible to be dropped on `2021-09-21 17:00:00` | |||
|
|
|||
| {{< info >}} | |||
| Starting Vitess `v20``, the table naming format will change. Tables will be named like so: | |||
There was a problem hiding this comment.
Extra trailing backtick after v20:
Starting in Vitess `v20`, the table naming format will change. Tables will be named like so:
| - `_vt_evc_6ace8bcef73211ea87e9f875a4d24e90_20200915120410_` | ||
| - `_vt_drp_6ace8bcef73211ea87e9f875a4d24e90_20200915120410_` | ||
|
|
||
| Version `v19` supports the new naming format, but does not generate any tables in this format. Version `v20` will generate tables in the new format, and will support the old format. Support for old format will be dropped in `v21` or later. |
There was a problem hiding this comment.
I don't think we need to say Version vX as the v in vX is for version. It's fine, but feels a little redundant to me. Personally I would prefer Vitess v19 over Version v19.
Signed-off-by: Shlomi Noach <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a
v19preliminary documentation of the new internal table names format, specifically in Table Lifecycle. See story in vitessio/vitess#14582 and changes in vitessio/vitess#14613.Nothing changes in
v19other than hidden support for new naming.