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
Describe the bug
With the cost-based optimizer enabled, there is a CPU projection between two GPU BroadcastHashJoin operators, which does not make sense.
Steps/Code to reproduce bug
Decimals enable, AQE on, CBO on. SF=3k.
Expected behavior
Projection should stay on GPU.
Additional context
None
The text was updated successfully, but these errors were encountered:
I tracked the issue down and it was an integer overflow when estimating the size of data that an operator would produce. The estimated row counts were extremely high, which is why I could only reproduce this on a large data set.
Describe the bug
With the cost-based optimizer enabled, there is a CPU projection between two GPU BroadcastHashJoin operators, which does not make sense.
Steps/Code to reproduce bug
Decimals enable, AQE on, CBO on. SF=3k.
Expected behavior
Projection should stay on GPU.
Additional context
None
The text was updated successfully, but these errors were encountered: