ameyabapat
New Contributor II

I still see the above error with databricks jdbc driver 2.6.33. Anyone aware of fix available either in  driver or java?