-
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
inl_join hints has wrong warrings in the cte query block #53767
Labels
affects-6.5
affects-7.1
affects-7.5
affects-8.1
severity/moderate
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Comments
Damon-Guo
changed the title
inl_join hint has wrong warrings in the cte query block
inl_join hints has wrong warrings in the cte query block
Jun 3, 2024
the same as #53454 |
jebter
added
sig/planner
SIG: Planner
duplicate
Issues or pull requests already exists.
labels
Jun 4, 2024
hawkingrei
added
severity/moderate
and removed
duplicate
Issues or pull requests already exists.
labels
Jun 6, 2024
13 tasks
This was referenced Jun 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-7.1
affects-7.5
affects-8.1
severity/moderate
sig/planner
SIG: Planner
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
The hint is worked, but it has some wrong warnings.
2. What did you expect to see? (Required)
the explain use index join without warnings.
3. What did you see instead (Required)
the explain use index join with warnings
There are no matching table names for (e) in optimizer hint /*+ INL_JOIN(e, e) / or /+ TIDB_INLJ(e, e) */. Maybe you can use the table alias name
4. What is your TiDB version? (Required)
Release Version: v8.1.0
Edition: Community
Git Commit Hash: 945d07c
Git Branch: HEAD
UTC Build Time: 2024-05-21 03:51:57
GoVersion: go1.21.10
Race Enabled: false
Check Table Before Drop: false
Store: tikv
The text was updated successfully, but these errors were encountered: