[GitHub] [airflow] potiuk commented on issue #29304: Mismatch of taskinstances executed for dagrun result in API vs web UI

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk commented on issue #29304:
URL: https://github.com/apache/airflow/issues/29304#issuecomment-1413714902

   I believe this is because previously you had "query_snowflake" task in your DAG that has been renamed to "snowflake_query" (notice that the UI si "snowflake_query" and in the API response you have "query_snowflake".
   
   Airflow does not currently support renaming of tasks and generally versioning (this might get implemented with https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-36+DAG+Versioning) at some point of time and the effect of renaming tasks is exactly what you see:
   
   * UI shows only the "current" state of the DAG (i.e. does not show "query_snowflake" task because it does not exist in the "current" DAG structure
   * API however shows all the tasks that have been executed when the DAG was executed (at that time "query_snowflake" was part of the DAG.
   
   You can verify that by adding a new tasl "query_snowflake" to your DAG or renaming it back - then the tasks executed in the past for "query_snowflake" will start showin up.
   
   The current recomendation when you remove tasks from DAG or change the structure significantly is to also change DAG_ID (effectively creating a new DAG) because we have currently not even a good way of showing history for such DAG  (until AIP-36 gets implemented).
   
   
   J.


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org