Request failed while connecting to Azure Databricks using usql
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
Start by reproducing the reported usql command against Azure Databricks and compare its behavior with the working DBeaver connection. Inspect the driver’s connection and URL-redirect handling, using the attached error log as the failure reference. Done means identifying the cause and making the same credentials and endpoint connect successfully, or documenting the confirmed limitation.
Written by the indexing model from the issue text.
Description
I am facing an issue when trying to connect to Databricks using usql. Even when using the correct credentials, typing the command:
usql databricks://token:dapi*****@adb-*************.azuredatabricks.net:443/sql/protocolv1/o/*********/*******
The credentials and URL details have been omitted for security, but I assure you that the data is correct.
Error Logs:
What You Have Tried
- Verified credentials and URLs.
- Reinstalled usql.
- Tried on different terminals and operating systems (MacOS and Linux).
Where it works
Using DBeaver and the same credentials, the connection works like a charm
Any help to resolve this issue would be highly appreciated.
Alternative question:
It seems to me that the driver redirects the Azure URL to the Databricks URL.
- Dominant language
- Go
- Stars
- 53
- Forks
- 67
- Avg merge
- 21h 29m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from databricks/databricks-sql-go
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
databricks/databricks-sql-go#476 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 64/100
databricks/databricks-sql-go#490 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
databricks/databricks-sql-go#481 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
databricks/databricks-sql-go#480 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
databricks/databricks-sql-go#475 · 1 comment ·
Maintainers usually reply within 1 day
All issues in databricks/databricks-sql-go
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[E2E Scenario Tests] HTTP logs capture export requests from test framework, polluting golden filesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
GoogleCloudPlatform/k8s-config-connector#13675 ·
Maintainers usually reply within 1 day
-
ai-inspected
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day