[GitHub] [airflow] howardyoo opened a new issue #21114: Better terminology for Airflow's execution start and end date

[GitBox <gi...@apache.org>]

howardyoo opened a new issue #21114:
URL: https://github.com/apache/airflow/issues/21114


   ### Apache Airflow version
   
   2.2.3 (latest released)
   
   ### What happened
   
   In the future releases, the terminology around how Airflow defines start and end of its `execution` **should be more clearly defined to avoid constant confusion**. I would like to suggest completely replacing the term with `data interval` for better clarity of what it refers to, in the documentation and source code of airflow.
   
   As mentioned in https://stackoverflow.com/questions/67251814/airflow-execution-date-is-confusinghttps://stackoverflow.com/
   questions/67251814/airflow-execution-date-is-confusing, the term 'execution' is confusing since many users assume the term `execution` as when the DAG is `executing.` Obviously this has been a constant misunderstanding as execution date simply refers to the period of which the DAG run is going to be basing its processing on.
   
   There is a new term to remedy the `execution` by replacing it with `logical date.` However, the term `logical` is also ambiguous as users may not know the context of which why this is supposed to be `logical.` Therefore, I would like to raise a feature request (if there hasn't been any as there yet) to come up with a better terminology to describe it.
   
   I saw in the Airflow UI which describes the execution date as `data interval` as such:
   ![image](https://user-images.githubusercontent.com/32691630/151105870-83f51650-d134-475a-9d80-8825b2fa0246.png)
   
   Which, in my opinion, is a far better and accurate term to describe the period of which the DAG run would be basing its processing against. Therefore, I would like to have the existing term `execution date` be deprecated, and gradually be replaced by `data interval` for better clarity.
   
   ### What you expected to happen
   
   the term `execution` to describe the period of which the DAG is going to run its orchestration against, is often misleading and confusing. Users would typically think the `execution` start and end date is DAG's run start and end date, and would often get confused when they see different dates on it execution and the DAG's start of the run.
   
   ### How to reproduce
   
   Ask any airflow users about what they think about what airflow's execution date means. You will hear many incorrect description of it. If you also talk about it with experienced airflow users, they will often criticize how it is used.
   
   ### Operating System
   
   MacOS Monterey (Version 12.1)
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   _No response_
   
   ### Anything else
   
   This problems occurs constantly among the users. It also happens more to the first time users who are learning airflow.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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