Skip to content

Conversation

@dstandish
Copy link
Contributor

Don't bother depickling {} object in dag run conf

Also, set the statement timeout a little higher for xcom migration.

Co-authored-by: Jed Cunningham 66968678+jedcunningham@users.noreply.github.com

(cherry picked from commit f75b607)

…pache#50788)

Don't bother depickling `{}` object in dag run conf

Also, set the statement timeout a little higher for xcom migration.

Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
(cherry picked from commit f75b607)
Copy link
Member

@ashb ashb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this is a backport, so go ahead and merge anyway, but do we not also need a bulk update of setting the conf to }} when it equals the empty pickle string, else it will be left as a pickle value?

@kaxil kaxil added this to the Airflow 3.0.4 milestone Jul 22, 2025
@dstandish dstandish merged commit dd2e3d2 into apache:v3-0-test Jul 22, 2025
56 checks passed
@dstandish dstandish deleted the cherry-pick-f75b607 branch July 22, 2025 18:17
@dstandish
Copy link
Contributor Author

I know this is a backport, so go ahead and merge anyway, but do we not also need a bulk update of setting the conf to }} when it equals the empty pickle string, else it will be left as a pickle value?

i'm a little confused -- can you try to clarify?

@ashb
Copy link
Member

ashb commented Jul 22, 2025

@dstandish What happens to the values that were a pickled version of {}? (sorry, typo, }} should have been {})

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants