Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error while executing queries #188

Open
ezbercihk opened this issue Jan 18, 2024 · 2 comments
Open

Error while executing queries #188

ezbercihk opened this issue Jan 18, 2024 · 2 comments

Comments

@ezbercihk
Copy link

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:

"error":"databricks: driver error: error performing staging operation: Invalid OperationHandle: OperationHandle [opType=EXECUTE_STATEMENT, getHandleIdentifier()=86608ab4-3f84-45d4-8401-e6c10c6fd758]","time":"2024-01-17T18:46:16Z","message":"databricks: failed to execute query: query SELECT 1"

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!

@ezbercihk
Copy link
Author

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.

@ezbercihk
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant