Different error handling behavior after DB runtime upgrade from 13.3 to 14.3

Karlo_Kotarac
Databricks Partner

Hi! We want to upgrade the DB runtime on our clusters from 13.3 LTS to 14.3 LTS. Currently, everything looks good except for the different error-handling in the new runtime.

For example, the error in the 13.3 LTS runtime looks familiar:

Karlo_Kotarac_0-1717743717317.png

while the same code on 14.3 LTS runtime throws the following error:

Karlo_Kotarac_1-1717743788282.png

Only after digging deeper into error logs, can I see that the error is the same in this case:

Karlo_Kotarac_3-1717743912995.png

Not sure if it is important information but we use the spark.sql() function when calling merge into command. Is there a way to restore the previous error-handling behaviour because current errors are not informative?