document global keyspace flag #1271
Draft
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: Max Englander <[email protected]>
rsajwani
reviewed
Dec 7, 2022
|
|
||
| #### With a default keyspace | ||
|
|
||
| With the default keyspace set to `customer` we can only query keyspace-unqualified tables in `commerce` i.e `customer` and `corder`. |
There was a problem hiding this comment.
shouldn't it be
"keyspace-unqualified tables in customer"
instead of
"keyspace-unqualified tables in commerce"
|
Returning this to draft status until there's more clarity around next steps for vitessio/vitess#11938 |
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.
Accompanies vitessio/vitess#11876.
Description
Vitess supports globally routing queries to unique tables when the connection does not have a default keyspace and the tables in the
FROMlist are not keyspace-qualified.This adds support for explicitly requesting global routing:
Use cases
This feature is useful for frameworks like Hibernate which are required by to set a database name on the connection. Those frameworks are unable to take advantage of global routing.