-
Notifications
You must be signed in to change notification settings - Fork 16.6k
Closed as not planned
Labels
airflow3.0:breakingCandidates for Airflow 3.0 that contain breaking changesCandidates for Airflow 3.0 that contain breaking changesairflow3.0:candidatePotential candidates for Airflow 3.0Potential candidates for Airflow 3.0area:db-migrationsPRs with DB migrationPRs with DB migrationarea:logging
Description
Body
Currently we do some “smart” (in quotes because it’s not actually very smart) detection whether a log template uses Python format string (e.g. {foo}-{bar}) or Jinja2 template syntax. We should find a way to remove the former as a feature and just always use Jinja2.
(Below is copied from another discussion)
The problem is we do record the log file template on DagRun so we could find the correct logs for an old run. Either we somehow find a way to distinguish those old runs (add a flag in db?) or we need to convert those old template strings into Jinja format in a db migration.
Committer
- I acknowledge that I am a maintainer/committer of the Apache Airflow project.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
airflow3.0:breakingCandidates for Airflow 3.0 that contain breaking changesCandidates for Airflow 3.0 that contain breaking changesairflow3.0:candidatePotential candidates for Airflow 3.0Potential candidates for Airflow 3.0area:db-migrationsPRs with DB migrationPRs with DB migrationarea:logging