nathadfield opened a new pull request, #67285:
URL: https://github.com/apache/airflow/pull/67285
Today, consumers of partitioned assets receive ``partition_key`` (str) but
``partition_date`` (datetime) is ``None`` on the consumer DagRun, so every
consumer has to parse the key string by hand. This PR carries the datetime form
alongside the string so consumers can use the canonical filter idiom in
templates:
```sql
WHERE dt = "{{ partition_date | ds }}"
```
- Producer side: ``AssetEvent.partition_date`` is stamped from
``ti.dag_run.partition_date`` at emission.
- Mapper-aware target date: computed once at APDR creation in
``assets/manager.py:_queue_partitioned_dags`` and stored on
``AssetPartitionDagRun.partition_date``; the scheduler copies it directly into
the consumer DagRun. ``IdentityMapper`` passes the source date through; the
``StartOf*Mapper`` family normalises via a new internal
``to_downstream_normalized``. Other mappers leave ``partition_date=None``.
- Output-only: not accepted on trigger payloads, so manual triggers cannot
create inconsistent ``(partition_key, partition_date)`` pairs.
- Surfaced through to consumer ``Context["partition_date"]`` (via
``coerce_datetime``), the execution-API ``DagRun`` / ``AssetEventResponse`` /
``DagRunAssetReference`` schemas (Cadwyn-versioned to strip the field for older
Task SDK clients), the core-API ``DAGRunResponse``, OTel span attributes, and
the standard provider's ``PythonVirtualenvOperator`` /
``ExternalPythonOperator`` serializable-context allow-list.
closes: #67239
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Opus 4.7) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
