Skip to content

Conversation

@dstandish
Copy link
Contributor

In 2.x, it was expected that this field was valid json -- e.g. "0 0 * * *".

In 3.x, the column is renamed and repurposed and not json.

So if we downgrade it, we need to null it out. It will get updated when dag is reserialized.

If we don't do this, the scheduler crashes.

In 2.x, it was expected that this field was valid json -- e.g. `"0 0 * * *"`.

In 3.x, the column is renamed and repurposed and not json.

So if we downgrade it, we need to null it out.  It will get updated when dag is reserialized.

If we *don't* do this, the scheduler crashes.
@dstandish dstandish merged commit 1bad247 into apache:main Apr 22, 2025
53 checks passed
@dstandish dstandish deleted the fix-downgrade-re-dag-model branch April 22, 2025 20:30
@dstandish dstandish added this to the Airflow 3.0.1 milestone Apr 22, 2025
kaxil pushed a commit that referenced this pull request Apr 23, 2025
In 2.x, it was expected that this field was valid json -- e.g. `"0 0 * * *"`.

In 3.x, the column is renamed and repurposed and not json.

So if we downgrade it, we need to null it out.  It will get updated when dag is reserialized.

If we *don't* do this, the scheduler crashes.

(cherry picked from commit 1bad247)
prabhusneha pushed a commit to astronomer/airflow that referenced this pull request Apr 25, 2025
In 2.x, it was expected that this field was valid json -- e.g. `"0 0 * * *"`.

In 3.x, the column is renamed and repurposed and not json.

So if we downgrade it, we need to null it out.  It will get updated when dag is reserialized.

If we *don't* do this, the scheduler crashes.
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.

2 participants