Bug #100000 Provide an index hint that only affects the choice of index for NL join

Submitted: 26 Jun 2020 7:58 Modified: 26 Jun 2020 8:38
Reporter: Øystein Grøvlen Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Server: Optimizer Severity:S4 (Feature request)
Version:8.0, 8.4 OS:Any
Assigned to: CPU Architecture:Any

[26 Jun 2020 7:58] Øystein Grøvlen
Description:
The new index hint JOIN_INDEX, does not only impact what index is used for join, but also for e.g. range access.  Cosider the following query:

mysql> explain select * from country join city on country.code = city.countrycode where country.code in ('CHN', 'IND', 'JPN') and city.population > 10000000;
+----+-------------+---------+------------+--------+-----------------+---------+---------+------------------------+------+----------+------------------------------------+
| id | select_type | table   | partitions | type   | possible_keys   | key     | key_len | ref                    | rows | filtered | Extra                              |
+----+-------------+---------+------------+--------+-----------------+---------+---------+------------------------+------+----------+------------------------------------+
|  1 | SIMPLE      | city    | NULL       | range  | CountryCode,idx | idx     | 4       | NULL                   |    1 |     5.00 | Using index condition; Using where |
|  1 | SIMPLE      | country | NULL       | eq_ref | PRIMARY         | PRIMARY | 3       | world.city.CountryCode |    1 |   100.00 | NULL                               |
+----+-------------+---------+------------+--------+-----------------+---------+---------+------------------------+------+----------+------------------------------------+

If we do not want the PRIMARY index of country to be used for the join (e.g., to force hash join to be used), we can try to use the hint JOIN_INDEX to avoid that:

mysql> explain select /*+ NO_JOIN_INDEX(country PRIMARY) */ * from country join city on country.code = city.countrycode where country.code in ('CHN', 'IND', 'JPN') and ci
ty.population > 10000000;
+----+-------------+---------+------------+-------+-----------------+------+---------+------+------+----------+--------------------------------------------+
| id | select_type | table   | partitions | type  | possible_keys   | key  | key_len | ref  | rows | filtered | Extra                                      |
+----+-------------+---------+------------+-------+-----------------+------+---------+------+------+----------+--------------------------------------------+
|  1 | SIMPLE      | city    | NULL       | range | CountryCode,idx | idx  | 4       | NULL |    1 |     5.00 | Using index condition; Using where         |
|  1 | SIMPLE      | country | NULL       | ALL   | NULL            | NULL | NULL    | NULL |  239 |     0.42 | Using where; Using join buffer (hash join) |
+----+-------------+---------+------------+-------+-----------------+------+---------+------+------+----------+--------------------------------------------+

Note that this also prevents PRIMARY to be used as range access when country is input to hash join.

How to repeat:
Using the world database:

explain select * from country join city on country.code = city.countrycode where country.code in ('CHN', 'IND', 'JPN') and city.population > 10000000;

explain select /*+ NO_JOIN_INDEX(country PRIMARY) */ * from country join city on country.code = city.countrycode where country.code in ('CHN', 'IND', 'JPN') and city.population > 10000000;

Suggested fix:
Let JOIN_INDEX hint only affect choice of index for NL join.  Let the general INDEX hint not affect the choice of index for NL join.  Alternatively, introduce a new hint, e.g., NL_JOIN_INDEX.
[26 Jun 2020 8:38] MySQL Verification Team
Hello Øystein,

Thank you for the feature request!

regards,
Umesh

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.058 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.