ashb commented on pull request #15285: URL: https://github.com/apache/airflow/pull/15285#issuecomment-819429445
> there has been periodic discussion on mailing list re adding support for stateful tasks and of late some renewed interest in the topic. adding DagState and TaskState classes would potentially be in conflict with that. if we do create stateful tasks, i think that TaskState as the model through which we store state (i.e. an artifact representin the task's state) would be a better usage of the word than an enum representing the execution state. I think the "stateful" tasks doesn't conflict with this -- Airflow essentially has a state-machine (if a _very_ poorly defined one) for what states a TI/DR can be in, so adding a whole new state is more work than just changing the value in the DB column, so by making this an explicit enum class it would hopefully make it clearer that you can't make up your own values to store in ti.state and expect it to Just Work. -- 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. For queries about this service, please contact Infrastructure at: [email protected]
