Ben Cassell
Ben Cassell
Sorry this took so long; please give 1.8.0b1 a shot: https://github.com/databricks/dbt-databricks/discussions/595
I'm fairly sure we imported/inherited this behavior from dbt-spark. At this point I have no idea why the limitation exists, so I will discuss with my team about lifting it.
I'm in favor of removing the limitation, but haven't had time to comb the code to understand impact. There may be a couple of places where we assume a fixed...
Will be part of 1.10.0
Thanks for the report. If you'd like to work on a PR to address, I'd be happy to help; otherwise due to resource constraints, this bug will probably not be...
Closing in favor of #897
There are a number of retries that happen before you even see an error, so it kind of depends on what sort of error that's surfacing. Do you have an...
This will come in 1.9; we've become conservative about when we upgrade our dependency versions due to major issues in the migration to 3.0, since users on Databricks Workflows will...
This bug only exists in old versions, as newer versions pin the SDK to a particular known-good version. What are the reasons you are pinned to old versions? I cannot...
@case-k-git when you say the processing stops working, I need to know specifically how so that I can fix it. We will never be able to go back to old...