Include node_info in SQLQueryStatus

[colin-rogers-dbt]

Describe the feature

dbt-core SQLQueryStatus includes an optional node_info field. Currently dbt-databricks does not populate it when firing the event. Doing so makes it easier for consumers to utilize the logs.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

dbt-core example: https://github.com/dbt-labs/dbt-core/blob/d91265411061463b42d6f4d6d94e094a42a96d2b/core/dbt/adapters/sql/connections.py#L83

Who will this benefit?

What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly.

Are you interested in contributing this feature?

Let us know if you want to write some code, and how we can help.

[davidharting]

@colin-rogers-dbt I am noticing that the SqlQuery events also expect to have node_info supplied and currently do not.
Would it be possible for you to apply a similar improvement to these events? The call sites are very close to the SQLQueryStatus events you already updated.

• Call site 1
• Call site 2

[colin-rogers-dbt]

@benc-db we should reopen this issue, looks like me prior fix missed SQLQuery events

[benc-db]

@colin-rogers-dbt I believe we can reclose now, with #494 right?