@potiuk - looks like this PR breaks get_first and get_records return type for snowflake for example , so instead of tuple we get a Dict.
this also breaks SqlSensor as it expects this first_cell = records[0][0]

this code - was getting the default cursor from the connection (SnowFlakeCursor) - but now is in the hands of the specific hook , which in snowflake case return a DictCursor

 with closing(conn.cursor()) as cur:
                results = []
                for sql_statement in sql:
                    self._run_command(cur, sql_statement, parameters)

                    if handler is not None:
                        result = handler(cur)
                        results.append(result)

Use latest version of both Airflow and Snowflake provider. There were several fixes implemented after that one.

Just make sure to upgrade everything to latest versions as they contain latest fixes.

And make sure to fix any deprecation warnings you see and look at the release notes - of Snowflake provider. There were a few breaking changes that you might want to fix (some of the things could be one of them).

@potiuk - thanks , i kinda figure that out after trying to play with different versions of common-sql and provider.
what surprised me is that we used to get a tuple, then after upgrading some of the providers we got dict.
and now latest version basically support both if a hook parameter is passed for returnning dictionary - meaning default is back to tuple. - what a mess:-)

back to tuple. - what a mess:-)

No. It is actually common right now. We use to have mess in the PAST . Now it's all straightforward. And the "other" options (like Dictionary) are only for those who want to have backwards compatibility. Mess is mainly because user want to stick to old ways even if we make things better organized and prefer to stay with the messy way it was before.

So if you want to avoid the mess - convert your code to use tuples and you will be good and everything will be straightend u for you (as is for users who are starting now and everything is the same for all DBAPi Hooks)

Also if you want to know why - you can read more of the architectural decisions made here: #36015

They explain how we straightened up the mess.

@potiuk - i think i came out wrong - i really appreciate what have being done (sticking with standard DBAPI)
the thing is meant is - we used to have tuple, then upgraded and got dict , now we understand tuple is the desired.

anyway - i'm trying to use the latest and greatest , in addition i'm using astronomer async operators - but now
i get this weird error which i cant understand how its possible .

super().__init__(conn_id=snowflake_conn_id, **kwargs)
E       TypeError: airflow.providers.common.sql.operators.sql.SQLExecuteQueryOperator.__init__() got multiple values for keyword argument 'conn_id'

Not suure - might be problem with the async operators