-
Notifications
You must be signed in to change notification settings - Fork 4
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
Unable to establish connection to Livy endpoint with error 408 #19
Comments
Are you always getting this error? There shouldn't be any additional config needed. |
@jcvdodson no, now with same code I'm getting error 404 |
Hmm, that's interesting. Have you double-checked your workspace_id and lakehouse_id in the profiles yml? |
yes, I have checked connection by calling List tables as it includes both workspace_id and lakehouse_id, and it works fine. I learned about the dbt-fabricspark adapter from dbt channel on Slack where @prdpsvs mentioned that Livy endpoints are in private preview and I should contact our Microsoft account team to sign up for the preview which I have done. Could be that something else needs to be done to activate it for our Fabric capacity. |
If you are able to create Lakehouses, you should be okay as far as Fabric capacity. Livy might have additional restrictions, but given that Synapse also uses Livy, you should also be good there. If you'd like, you can email me at [email protected] and I can see if I am able to reproduce this issue. |
Hi were you able to fix it? |
Have you signed up for the Livy Public Preview? |
Not Yet :) |
I'm too unable to establish a connection to Livy endpoint with error 404 by using the dbt-fabric adapter. |
Trying to materialize a model with the dbt-fabric adapter. It fails to establish connection to Livy endpoint and times out at create_session
Error message:
Http Error: 408 Client Error: Request Timeout for url: https://api.fabric.microsoft.com/v1/workspaces/{workspace_id}/lakehouses/{lakehouse_id}/livyapi/versions/2023-12-01/sessions
Call to other endpoints, like List tables works fine.
Is there any configuration that needs to be done to make it to work?
The text was updated successfully, but these errors were encountered: