phanikumv commented on code in PR #63419: URL: https://github.com/apache/airflow/pull/63419#discussion_r2974026326
########## airflow-core/newsfragments/63419.significant.rst: ########## @@ -0,0 +1,34 @@ +AIP-76: Asset Partitioning + +Airflow 3.2 introduces asset partitioning (time-based), allowing DAGs to produce and consume +partitioned asset events identified by a ``partition_key`` (e.g. ``2026-03-10T09:00:00`` for +an hourly partition, or ``us|2026-03-10T09:00:00`` for a composite key). + +**New timetables** (``airflow.timetables.partitioned``): + +- ``CronPartitionTimetable`` — schedules a producer DAG on a cron expression and emits a + partitioned asset event on each run. +- ``PartitionedAssetTimetable`` — schedules a consumer DAG when the expected partitioned + asset events have arrived. + +**Partition mappers** transform upstream partition keys before passing them to downstream DAGs: Review Comment: Done ########## airflow-core/newsfragments/63419.significant.rst: ########## @@ -0,0 +1,34 @@ +AIP-76: Asset Partitioning + +Airflow 3.2 introduces asset partitioning (time-based), allowing DAGs to produce and consume +partitioned asset events identified by a ``partition_key`` (e.g. ``2026-03-10T09:00:00`` for +an hourly partition, or ``us|2026-03-10T09:00:00`` for a composite key). + +**New timetables** (``airflow.timetables.partitioned``): + +- ``CronPartitionTimetable`` — schedules a producer DAG on a cron expression and emits a + partitioned asset event on each run. +- ``PartitionedAssetTimetable`` — schedules a consumer DAG when the expected partitioned + asset events have arrived. + +**Partition mappers** transform upstream partition keys before passing them to downstream DAGs: + +- ``IdentityMapper`` — passes the key through unchanged (default). +- ``HourlyMapper``, ``DailyMapper``, ``WeeklyMapper``, ``MonthlyMapper``, ``QuarterlyMapper``, + ``YearlyMapper`` — normalize a datetime partition key to a coarser time granularity Review Comment: Done -- 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]
