docs: Document tablet-specific targeting syntax for USE statements #2041
Conversation
This file contains hidden or 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
✅ Deploy Preview for vitess ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Collaborator
|
@Promptless it looks like you removed a bunch about window functions somewhere along the way. This PR should just be adding information about tablet targetig. |
Contributor
Author
|
I've added new changes to address this PR comment in commit 73f2050 |
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.
Added documentation for the new tablet-specific targeting feature introduced in PR #18809. Users can now route queries to a specific tablet by its alias using the syntax
USE keyspace:shard@tablet_type|tablet-alias(e.g.,USE mykeyspace:-80@replica|zone1-0000000100). This feature is useful for debugging and troubleshooting scenarios where stable routing to a specific tablet is needed when direct MySQL access isn't available.Trigger Events
Open this suggestion in the Promptless dashboard
Help us improve Promptless — If this suggestion missed the mark, please share quick feedback.
If you want Promptless to make further changes on this PR, feel free to leave a comment tagging Promptless (It won't show up in the user drop down but Promptless will get it!)