jason810496 commented on issue #62564:
URL: https://github.com/apache/airflow/issues/62564#issuecomment-4045553443

   Hi @guan404ming,
   Would it be possible for you to provide some additional context about the 
related change, or explain how the “Partitioned Runs” feature works please?
   
   Also, how could I reproduce the environment (Dags or steps) used in? I 
still haven’t been able to reproduce the conditions needed to show the 
“Partitioned Runs” tab, as demonstrated in the video in 
https://github.com/apache/airflow/pull/61398.
   Thank you very much!
   
   Right now, the only way I can fix this is by adding a dedicated “Partitioned 
Runs” tab on the DagRun page ( which I’d like to avoid, since adding a 
dedicated tab would just duplicate existing components )
   
   The only thing I know so far is that we need to fix the semantic meaning of 
‎`dag_model.timetable_partitioned` on the API side.
   However, the API side patch is not enough to solve the error.
   ```patch
   index 155b49726f..78a8188596 100644
   --- a/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/assets.py
   +++ b/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/assets.py
   @@ -55,7 +55,7 @@ def next_run_assets(
        pending_partition_count: int | None = None
    
        queued_expr: ColumnElement[int]
   -    if is_partitioned := dag_model.timetable_summary == "Partitioned Asset":
   +    if is_partitioned := dag_model.timetable_partitioned:
            pending_partition_count = session.scalar(
                select(func.count())
                .select_from(AssetPartitionDagRun)
   diff --git 
a/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/partitioned_dag_runs.py
 
b/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/partitioned_dag_runs.py
   index f9090a6ece..b233f3d543 100644
   --- 
a/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/partitioned_dag_runs.py
   +++ 
b/airflow-core/src/airflow/api_fastapi/core_api/routes/ui/partitioned_dag_runs.py
   @@ -71,7 +71,7 @@ def get_partitioned_dag_runs(
            # Single query: validate Dag + get required count
            dag_info = session.execute(
                select(
   -                DagModel.timetable_summary,
   +                DagModel.timetable_partitioned,
                    
func.count(DagScheduleAssetReference.asset_id).label("required_count"),
                )
                .outerjoin(
   ```
   
   


-- 
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]

Reply via email to