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

Fix treament of dual as sharded by reverting #5268 #5519

Closed
wants to merge 2 commits into from

Conversation

aquarapid
Copy link
Contributor

Fixes #5508

I think we should fix the problem in #5268 by just implementing "SELECT 1 from dual" in vtgate.

This reverts commit 27b5aae.

Signed-off-by: Jacques Grove <aquarapid@gmail.com>
@systay
Copy link
Collaborator

systay commented Dec 6, 2019

+1 #5268 is "just" a performance optimisation, but it's broken quite a few scenarios. I'm currently working on shortcutting dual calls, so this will work soon enough. Until then, this revert is what we should do, IMHO.

/cc @mpawliszyn

@sougou
Copy link
Contributor

sougou commented Dec 13, 2019

Closing in favor of #5551

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.

Vitess seems to treat inserts with subselects involving DUAL as sharded, even when keyspace is unsharded?
3 participants