You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] choose broadcastjoin first when cardinality cannot be estimated #4149
sql: select * from (select k1 from jointest group by k1)t2, jointest t1 where t1.k1 = t2.k1
reason:
In version 0.11, the SQL choose broadcastjoin and returns it in 9s. However, in version 0.12, the SQL choose shuffle join and runs 32S.
When the cardinality cannot be estimated, it is better to choose broadcast join first. When there is a performance bottleneck, users can manually add hint to shuffle point.
changed the title [-]choose broadcastjoin first when cardinality cannot be estimated[/-][+][BUG] choose broadcastjoin first when cardinality cannot be estimated[/+]on Jul 23, 2020
Activity
[-]choose broadcastjoin first when cardinality cannot be estimated[/-][+][BUG] choose broadcastjoin first when cardinality cannot be estimated[/+](hubspot 4.0.5) [Opt](cloud-mow) Do fast retry when commit compaction…