kacpermuda opened a new pull request, #65727:
URL: https://github.com/apache/airflow/pull/65727
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
On Airflow 3, tasks can emit asset events at runtime in several ways beyond
statically declaring inlets=/outlets= on the operator. Today OpenLineage only
sees the static declarations - anything the task produces dynamically is
invisible to OL unless a dedicated extractor or hook-lineage reader picks it up.
This PR closes this gap and adds those dynamic assets into:
- AirflowRunFacet.task.inlets / outlets — so the serialized task snapshot
reflects what actually ran.
- The OL job's inputs / outputs datasets (the "no extractor, no hook
lineage" fallback) - via the existing translate_airflow_asset converter,
deduped by (namespace, name) against static inlets/outlets and against each
other.
Static inlets / outlets behavior is unchanged. Dynamic assets are appended
to the static ones; nothing static is dropped, replaced, or rewritten. If a
task has no dynamic events, the emitted facet is identical to before.
Inlets are unaffected by this PR - Airflow has no runtime inlet_events
emission path that adds new inlets, so the static list remains the source of
truth on the input side.
There is also a small change to use `ProvidersManagerTaskRuntime` from task
sdk instead of legacy `ProvidersManager` from core, as it's raising deprecation
warning.
### How users emit these events
1. Via AssetAlias + outlet_events (alias resolved at runtime):
```
@task(outlets=[AssetAlias("my-alias")])
def producer(*, outlet_events):
outlet_events[AssetAlias("my-alias")].add(
Asset("s3://bucket/file.txt"), extra={"rows": 42}
)
```
-> OL outlet = `"[{'uri': 's3://bucket/file.txt', 'extra': {'rows': '42'},
'asset_type': 'asset_event_from_alias', 'source_alias': 'my-alias'}]"`
2. Via outlet_events directly on a statically-declared Asset (no alias):
```
@task(outlets=[Asset("s3://bucket/file.txt")])
def producer(*, outlet_events):
outlet_events[Asset("s3://bucket/file.txt")].extra = {"rows": 42}
```
-> OL outlet = `"[{'uri': 's3://bucket/file.txt', 'extra': {'rows': 42},
'asset_type': 'asset_event'}]"`
3. Via yield Metadata(...) from the task:
```
@task(outlets=[Asset("s3://bucket/file.txt")])
def producer():
yield Metadata(Asset("s3://bucket/file.txt"), extra={"rows": 42})
```
-> Same as .2 above
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [X] Yes (please specify the tool below)
Generated-by: Claude 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]
