Jesper Bagge

Would love for this to happen since table materializations fails using `dbt-core==1.2.0` and `dbt-clickhouse==1.1.7`

Well honestly, that makes us two. I created a fresh virtualenv using python3.9 and just ran `pip install dbt-clickhouse` which gave me ``` dbt-clickhouse==1.1.7 dbt-core==1.2.1 ``` And now I can't...

I think you should be able to apply the s3 engine config to all your models by using the general config pattern [documented here](https://docs.getdbt.com/reference/model-configs#general-configurations). ```yml models: subfolder-where-you-keep-your-models: +materialized: table +engine:...

Just wanted to chip in with what I came out with after a bit of a rabbit chase and how I got things to not repeatledy restart. On version 0.4.0...

> Are there any tools that i can use to convert the raw data to final tables meanwhile the support is coming for clickhouse in future. @abhishekgahlot2 ClickHouse comes with...

> JSONExtract as mentioned beats the purpose as we have quite a lot of tables and various sources too. @o1lab Yeah, I came to that conclusion myself in the end...

@pankajastro it seems that this deprecation is already considered, when looking at [this comment line](https://github.com/astronomer/astronomer-cosmos/blob/1854f9edcd6e5cfb21ac1b13ade420da9b96c2f9/cosmos/airflow/graph.py#L300). I guess it only gets weird when running `astronomer-cosmos==1.10` with `dbt-core==1.10`. I could probably downgrade...

Having the exact same issue with decimal and pyarrow as backend on `dlt==1.15`: ``` dlt.pipeline.exceptions.PipelineStepFailed: Pipeline execution failed at `step=extract` when processing package with `load_id=1759842696.634382` with exception: In processing pipe...

Today I discovered that an adapted version of [an example in the documentation](https://dlthub.com/docs/dlt-ecosystem/verified-sources/sql_database/configuration#pyarrow) actually became a workaround to my issue. I'm loading data from a MariaDB database that has some...

Thanks for the info, @rudolfix! However, it was @coisnepe that posted this issue. I was having the same issue but found a workaround. Still, wouldn’t it be great if apply_hints...