Disable test_dbt_base on odbc-sql-endpoint spec (for now) #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Offers temporarily relief from #133 (does not resolve)
Description
It seems that
set
statements no longer work on SQL Analytics endpoints, and we use them in theincremental
materialization. We'll bring this up with our contacts at Databricks.In the meantime, this PR totally disables
test_base
within theodbc-sql-endpoint
spec. We could override/reimplement it within the spec, to remove just the step whereswappable
ismaterialized: incremental
, but I don't think it's worth it. As I see it, the main purpose of having a dedicatedodbc-sql-endpoint
spec is:dbt-spark
functionality is not yet at parityChecklist
I have run this code in development and it appears to resolve the stated issueI have updated theCHANGELOG.md
and added information about my change to the "dbt next" section.