hussein-awala commented on PR #70225: URL: https://github.com/apache/airflow/pull/70225#issuecomment-6302499048
I tested this PR locally in Breeze. I ran producer and consumer Dags through the scheduler and inspected the UI. The consumer used six sensor configurations: - A concrete `Asset` with the minimum count policy. - A concrete `Asset` with the exact count policy. - An `AssetAlias`. - A name-only reference. - A URI-only reference. - A regexp filter with descending order, a limit, and `process_result`. The producer emitted three matching events and one event with a different partition key. The sensors used time, partition, and metadata filters. All eight consumer tasks succeeded, including all six sensors. The final task checked their XCom results and event counts. The inlet UI check found a remaining limitation. The asset page showed the three sensors that used concrete `Asset` targets under **Consuming Tasks**. It omitted the name-only and URI-only sensors. The asset reached through the alias also showed no consuming task. All three omitted sensors executed successfully. Core Dag processing currently [records these inlet links only for concrete serialized assets](https://github.com/apache/airflow/blob/89ce7a4ff70623044257a1c7a6acc3382d55c1a3/airflow-core/src/airflow/dag_processing/collection.py#L992-L995). It does not record the equivalent links for name references, URI references, or aliases. Thus, the inlet declaration satisfies the UI request for concrete assets only. References and aliases still need core support before their consuming tasks appear in the UI. -- 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]
