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
When our app starts up it runs the ping query (SELECT 1) to make sure we are able to run queries successfully and this is the error we got. We are unable to reproduce this in our environment when we use SQL warehouse or old classic Spark clusters. Our customer uses Spark clusters in govcloud so we are not able to replicate this issue. Their environment is a bit complex with http proxies involved as well but the previous version we used (1.3.0) did not have this problem. So somewhere between 1.3.0 and 1.5.2 a change that is introduced seem to be causing this issue. I would appreciate your help in finding out what might be the culprit as we are unable to upgrade our driver version going forward until this is resolved.
Thanks!
The text was updated successfully, but these errors were encountered:
We are working with our customer to pinpoint which version of the driver is causing this between 1.3.0 and 1.5.2. I'll update the issue with that information once we find out.
We managed to pinpoint to a version where it started to fail and it is 1.5.0. I'd appreciate your help with this as until this is resolved we will be stuck on 1.4.x
We recently upgraded our driver version from 1.3.0 to 1.5.2 and encountered the following error when one of our customers tried to deploy our product:
When our app starts up it runs the ping query (SELECT 1) to make sure we are able to run queries successfully and this is the error we got. We are unable to reproduce this in our environment when we use SQL warehouse or old classic Spark clusters. Our customer uses Spark clusters in govcloud so we are not able to replicate this issue. Their environment is a bit complex with http proxies involved as well but the previous version we used (1.3.0) did not have this problem. So somewhere between 1.3.0 and 1.5.2 a change that is introduced seem to be causing this issue. I would appreciate your help in finding out what might be the culprit as we are unable to upgrade our driver version going forward until this is resolved.
Thanks!
The text was updated successfully, but these errors were encountered: