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
In their initial launch, Python models are supported on three of the most popular data platforms: Snowflake, Databricks, and BigQuery/GCP (via Dataproc).
Is this issue therefore "please bring Python models to Redshift"?
Thanks for opening this issue @reletreby ! As noted by @owenprough-sift above, we don't currently support Python models in Redshift, and that is why you are getting that error message.
We do have an issue open for adding Python models, so I'm going to close this one as a duplicate. You can subscribe to it if you want to get notifications (see screenshot below for how to subscribe):
From docs:
"In a dbt Python model, all Python code is executed remotely on the platform. None of it is run by dbt locally. We believe in clearly separating model definition from model execution".
Is there a way to specify where python code is run (at least for testing purposes) or pass an archive similar to aws lambda function setup?
This would be my next issue after postgres support is live)
Is this a new bug in dbt-core?
Current Behavior
Running a simple Python module (Amazon Redshift) gives
Materialization "materialization_table_default" only supports languages ['sql']; got "python"
The model I am running is
def model(dbt,session): dbt.config(materialized="table") return session.sql("select 'hello world' as message")
and I run it as
pipenv run dbt run --models intermediate.python_models.python_template --target qa
and I have the following versions
`Core:
Plugins:
Expected Behavior
I expect not to see this error as
python
should be supported!Steps To Reproduce
I have added information in the body of the issue above
Relevant log output
No response
Environment
Which database adapter are you using with dbt?
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: