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

[destination-databricks] connection to Azure Databricks - Error 504 with V3.1.0 #43712

Open
1 task
betizad opened this issue Aug 11, 2024 · 1 comment
Open
1 task
Labels
area/connectors Connector related issues community connectors/destination/aws-lakehouse Stale team/destinations Destinations team's backlog type/bug Something isn't working

Comments

@betizad
Copy link

betizad commented Aug 11, 2024

Connector Name

destination-databricks

Connector Version

3.1.0

What step the error happened?

Configuring a new connector

Relevant information

I'm trying to make a new connecion to a sql warehouse on Azure Databricks. The wareouse is not behind any firewall or vnet and is accessible diretly.
When trying to make a new connection:

  • I get HTTP error 401 while authenticating with PAT and setup fails.
  • I get FAILURE_OAUTH_REQUEST while authenticating with OAuth and setup fails.

I also do not find any logs in databricks workspace queries history, as if the warehouse has not been reached.

The setup documentation seems to be incomplete for azure databricks.

  • username and password are not valid in azure databricks and PAT should be sufficient
  • in OAuth mode, there is also a need for TenantId field

P.S. I am able to connect with V 1.1.0 but I would like to use refresh feature and incremental deduplication features in V3.
PAT_check_connection_destination-failure-37310705-ea7a-4c1e-a507-beacd7201ea7.txt
OAuth_check_connection_destination-failure-4784245b-19bb-4a7d-8908-15afff8a36fe.txt

Relevant log output

No response

Contribute

  • Yes, I want to contribute
@betizad betizad added area/connectors Connector related issues needs-triage type/bug Something isn't working labels Aug 11, 2024
@girarda girarda added team/destinations Destinations team's backlog and removed team/connectors-python labels Aug 21, 2024
@marcosmarxm marcosmarxm changed the title Databricks Lakehouse connection to Azure Databricks - Error 504 with V3.1.0 [destination-lakehouse] connection to Azure Databricks - Error 504 with V3.1.0 Sep 8, 2024
@marcosmarxm marcosmarxm changed the title [destination-lakehouse] connection to Azure Databricks - Error 504 with V3.1.0 [destination-databricks] connection to Azure Databricks - Error 504 with V3.1.0 Sep 8, 2024
@octavia-squidington-iii
Copy link
Collaborator

At Airbyte, we seek to be clear about the project priorities and roadmap. This issue has not had any activity for 180 days, suggesting that it's not as critical as others. It's possible it has already been fixed. It is being marked as stale and will be closed in 20 days if there is no activity. To keep it open, please comment to let us know why it is important to you and if it is still reproducible on recent versions of Airbyte.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues community connectors/destination/aws-lakehouse Stale team/destinations Destinations team's backlog type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants