pingcap / pingcap/tidb

LEADING hint cannot take effect when the subquery is the result of joins.

Open
#52,789 2 comments 0 reactions 1 assignee Claimed by @qw4990 View on GitHub
affects-7.1 affects-7.5 affects-8.1 affects-8.5 epic/hint epic/sql-plan-management report/customer sig/planner type/enhancement
Dominant language
Go
Stars
40.5k
Forks
6.2k
PR merge metrics
PR metrics pending

Description

## 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.