pingcap/tidb

Support to use the outer side of the (Anti) Semi Join to build the hash table

Open

#32.335 geöffnet am 14. Feb. 2022

Auf GitHub ansehen
 (9 Kommentare) (4 Reaktionen) (1 zugewiesene Person)Go (6.186 Forks)batch import
help wantedsig/plannertype/enhancement

Repository-Metriken

Stars
 (40.090 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 14T 4h) (346 gemergte PRs in 30 T)

Beschreibung

Enhancement

Currently, when TiDB meets a(an) (Anti) Semi join, it would always choose the inner side to build the hash table. When the inner side is extremely large compared with the outer side, our current strategy would cost a lot on building the hash table by the inner side.

So we should support constructing the hash table by the outer side to speed up the execution when the data distribution is like the above case.

It's something the same with supporting constructing hash table by the outer side of the outer join, which is implemented in TiDB.

Contributor Guide