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.
In
core.dbt.adapters.sql.connection
, we:get_response
is an abstract method which can returnUnion[AdapterResponse, str]
AdapterResponse
(an object with a_message
attribute) when we fireSQLQueryStatus
, ever since dbt-labs/dbt-core@b3039fdBefore this change,
dbt-spark
implementedget_response
in a super naive way (it just returns a string). This PR changes it to return anAdapterResponse
instead, with no functional change.In
dbt-core
, we should either:get_response
, then either use it_message
attribute (ifAdapterResponse
) or itself (ifstr
)get_response
abstract method must return anAdapterResponse
— not a bad change, and it's effectively true, but we should think about waiting for a minor version release with clearer communication ahead of time