-
Notifications
You must be signed in to change notification settings - Fork 14.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DatabricksSQLOperator struggles with parsing the data #36839
Comments
Indeed, a |
@Joffreybvn Just retested with
|
I could not reproduce your error. But I found another bug where a single namedtuple 'Row' fails to be serialized, while a list of those namedtuples works fine. Is your query returning only one result? |
Hi there. I'm running into this same issue. I'm running a merge statement that only returns one row with four columns. Appreciate your attention to this. Old versions: no error New versions; getting error
|
@odykstra any resolution on this issue? |
@avivshafir The newest versions should have fixed this issue. So check your versions and upgrade if possible. The other choice is to make your databricks provider version explicit in the requirements.txt file. I have my version held like so: but I know anything in version 5 does not have the issue also. |
Apache Airflow Provider(s)
databricks
Versions of Apache Airflow Providers
The error has not been present in version apache-airflow-providers-databricks==4.7.0
I upgraded to the latest and it is presentapache-airflow-providers-databricks==6.0.0
Apache Airflow version
2.8.0
Operating System
Debian GNU/Linux 11 (bullseye)
Deployment
Official Apache Airflow Helm Chart
Deployment details
No response
What happened
I did a little of investigation and edited
hooks/databricks_sql.py
file and added prints in the_make_common_data_structure
method:result
variable value:rows_fields
var value:What you think should happen instead
No response
How to reproduce
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: