-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
LEADING hint cannot take effect when the subquery is the result of joins. #52789
Labels
epic/hint
epic/sql-plan-management
sig/planner
SIG: Planner
type/enhancement
The issue or PR belongs to an enhancement.
Comments
winoros
added
type/enhancement
The issue or PR belongs to an enhancement.
sig/planner
SIG: Planner
labels
Apr 22, 2024
For the two table case, if we define the query block name for the subquery: |
There are other cases
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
epic/hint
epic/sql-plan-management
sig/planner
SIG: Planner
type/enhancement
The issue or PR belongs to an enhancement.
Enhancement
For the SQL
select ... from a, b on ... where a.xxx in (select yyy from c, d where ...)
, we cannot use the LEADING hint to control the join order between the main query and the in subquery.The text was updated successfully, but these errors were encountered: