ColtenOuO commented on issue #40055:
URL: https://github.com/apache/airflow/issues/40055#issuecomment-5388202534
In current Airflow 3, the job-table code path this issue describes no longer
exists.
- `BackfillJob` (the class that used to write a row to the `job` table for a
backfill run) was removed in #42943 ("Remove BackfillJobRunner class"), which
actually landed *before* the 3.0 release as cleanup ahead of the AIP-84 rewrite.
- Backfill now stores its state exclusively in the dedicated `backfill` /
`backfill_dag_run` tables, introduced by the
`0033_3_0_0_add_tables_for_backfill.py` and
`0037_3_0_0_add_backfill_to_dag_run_model.py` migrations and wired up via
#43496 (AIP-84, migrating the backfill API to FastAPI). `airflow dags backfill`
→ `backfill_command.py` → `_create_backfill()` only touches
`Backfill`/`BackfillDagRun` ORM objects now; it never creates a `Job` row.
- The `Job` model (`airflow-core/src/airflow/jobs/job.py`) still has
`dag_id` and `executor_class` columns, but the only job runners left are for
the scheduler, triggerer, and DAG processor — there's no backfill-type job
runner anymore, so this specific bug class can't recur.
- `Backfill.dag_id` is `NOT NULL` in the schema and is always passed a real
value at construction time in `_create_backfill()` — no path leaves it null.
Given the underlying `job`-table code this issue is about no longer exists.
I think maybe this issue can be close?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
