ashwanisin commented on issue #52438:
URL: https://github.com/apache/airflow/issues/52438#issuecomment-5157517371
Confirming this is still present in Airflow 3.3.0.
Same pattern as the original report: outlets=[AssetAlias(...)] on a task,
with outlet_events[alias].add(Asset(...), extra={...}) inside. airflow assets
list (CLI) correctly shows the dynamically-created assets, but GET
/api/v2/assets?limit=50&offset=0 (tested directly via curl with a valid bearer
token, no query filters) returns {"assets":[],"total_entries":0} — completely
empty.
I initially suspected the per-run-changing URI (each run generated a unique
file://.../timestamp_report.csv URI) was the cause. I switched to a stable name
and stable custom-scheme uri (e.g. x-myapp://included_report), with the actual
variable file path moved entirely into extra. Even with a fully stable name+URI
pair, GET /api/v2/assets still returns empty for these assets, while airflow
assets list (CLI) shows them correctly.
This rules out URI-churn as the cause and points more specifically at the
alias→asset link itself not being traversed by the REST API — consistent with
the original report here ("the asset alias doesn't have the necessary assets in
them"). The downstream scheduling (schedule=alias_a & alias_b on the consumer
DAG) continues to work correctly and triggers as expected regardless, so this
appears to be purely an API/UI visibility gap, not a core scheduling bug.
--
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]
