[Bug] status and rowcount not reported beginning with version `1.5.0` about dbt-redshift

[dataders]

@soroushmalek67 thanks for reporting this! This is an on-going regression due to a limitation of the redshift-connector Python driver. I've opened aws/amazon-redshift-python-driver#220 to request that SQL State be provided as a Cursor attribute.

Indeed this change began in #251, which was released initially in dbt-redshift 1.5.0. As @dave-connors-3 pointed out the status and rows modified comes from the driver's Cursor. there's a note on RedshiftConnectionManager.get_response()

redshift_connector.Cursor doesn't have a status message attribute but [because] this function is only used for successful run[s], so we can just return a dummy "SUCCESS"

dbt-redshift/dbt/adapters/redshift/connections.py

Lines 258 to 263 in ddfc36c

	def get_response(cls, cursor: redshift_connector.Cursor) -> AdapterResponse:
	# redshift_connector.Cursor doesn't have a status message attribute but
	# this function is only used for successful run, so we can just return a dummy
	rows = cursor.rowcount
	message = "SUCCESS"
	return AdapterResponse(_message=message, rows_affected=rows)

Other data platforms similarly do not provide this information, accordingly the respective dbt adapters lack this information, namely:

• dbt-spark & dbt-databricks (see dbt-labs/dbt-spark#497)
• dbt-sqlserver, dbt-synapse, dbt-fabric (see FabricConnectionManager.get_response())