Details
-
Task
-
Status: Stalled (View Workflow)
-
Major
-
Resolution: Unresolved
Description
Implement the new-style hints:
INDEX_MERGE
|
NO_INDEX_MERGE
|
in a way compatible to MySQL.
MySQL's Work Log: https://dev.mysql.com/worklog/task/?id=9167
Attachments
Issue Links
- split from
-
MDEV-33281 Implement optimizer hints like in MySQL 8
-
- In Progress
-
Activity
Field | Original Value | New Value |
---|---|---|
Component/s | Optimizer [ 10200 ] |
Labels | hints |
Fix Version/s | 12.0 [ 29945 ] |
Description |
Implement the new-style hints:
{code} INDEX_MERGE NO_INDEX_MERGE {code} |
Description |
Implement the new-style hints:
{code} INDEX_MERGE NO_INDEX_MERGE {code} |
Implement the new-style hints:
{code} INDEX_MERGE NO_INDEX_MERGE {code} in a way compatible to MySQL. MySQL's Work Log: https://dev.mysql.com/worklog/task/?id=9167 |
Link | This issue relates to MDEV-33281 [ MDEV-33281 ] |
Labels | hints | Compatibility hints mysql |
Assignee | Dave Gosselin [ JIRAUSER52216 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Fix Version/s | 12.1 [ 29992 ] | |
Fix Version/s | 12.0 [ 29945 ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Link | This issue split from MDEV-33281 [ MDEV-33281 ] |
Link | This issue relates to MDEV-33281 [ MDEV-33281 ] |
Both our code and the referenced MySQL work log mention not only index merge but also others (like index_merge_union). Judging from our code, it appears that codepaths where some index_merge_* optimizer switch is used are gated by the index merge option itself (as though it is a top-level switch) so it appears sufficient for the new hint to affect only index merge, and the others will either be enabled or disabled accordingly. Testing will bear it out and I'll update accordingly.