Fix upgrade failure when xcom contains NaN in string values#57614
Merged
Conversation
vatsrahul1001
approved these changes
Oct 31, 2025
dstandish
approved these changes
Oct 31, 2025
kaxil
pushed a commit
that referenced
this pull request
Oct 31, 2025
(cherry picked from commit 376ab5d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Nov 3, 2025
(cherry picked from commit 376ab5d)
ephraimbuddy
pushed a commit
that referenced
this pull request
Nov 4, 2025
(cherry picked from commit 376ab5d)
44 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes: #57608
Problem
When migrating from Airflow 2.x to 3.0, the migration
0049_3_0_0_remove_pickled_data_from_xcom_tablewas failing.This occurred when XCOM data contained the string "NaN" as part of a value, for example:
{"craft": "Tiangong", "name": "Ye GuangfuNaN"}The migration was using a simple
REPLACE()function that replaced all occurrences of'NaN'with'"nan"', which broke the JSON structure whenNaNappeared inside string values. The broken JSON would become:{"craft": "Tiangong", "name": "Ye Guangfu"nan""}And things would break.
I changed the
NaNsanitization to use regex with word boundaries to match only standaloneNaNtokens (like"key": NaN) while preservingNaNthat appears inside string values.regexp_replacewith word boundaries (\bNaN\b) (https://neon.com/postgresql/postgresql-string-functions/regexp_replace)REGEXP_REPLACEwith word boundaries ([[:<:]]NaN[[:>:]]) (https://dev.mysql.com/doc/refman/8.4/en/regexp.html)REPLACE()approach as sqlite doesn't have regex support(?)Testing
breeze start-airflow --backend postgres --executor CeleryExecutor --use-airflow-version 2.11.0 --db-resetbreeze start-airflow --backend postgres --executor CeleryExecutor --use-airflow-version 3.1.1No migration error:
^ Add meaningful description above
Read the [Pull Request Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull
-request-guidelines) for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.