You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See the comment in https://github.com/vitessio/vitess/pull/13750/files#r1337276087, and the surrounding test case changes for examples where the optimization was lost. It'd be great to bring this optimization back to ensure we don't end up loading thousands of rows when we already know the result as soon as the first row is returned.
Reproduction Steps
N/A
Binary Version
v18 and later
Operating System and Environment details
N/A
Log Fragments
N/A
The text was updated successfully, but these errors were encountered:
Overview of the Issue
When subqueries were moved to the operator model, Vitess stopped applying
LIMIT 1
onEXISTS
subqueries.See the comment in https://github.com/vitessio/vitess/pull/13750/files#r1337276087, and the surrounding test case changes for examples where the optimization was lost. It'd be great to bring this optimization back to ensure we don't end up loading thousands of rows when we already know the result as soon as the first row is returned.
Reproduction Steps
N/A
Binary Version
Operating System and Environment details
Log Fragments
The text was updated successfully, but these errors were encountered: