dstandish edited a comment on pull request #15285: URL: https://github.com/apache/airflow/pull/15285#issuecomment-819648630
> 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. I don't mean that the _two concepts_ conflict just that I would like to reserve the _name_ `TaskState` and `DagState`, potentially, for use with "stateful" tasks. just trying to think if there's a name we could use for the _execution_ states enum which would not clobber that. but, maybe owing to the fact that there already is an "execution state" concept, if "stateful tasks" is ever implememted it might be prudent to use the name "watermark" or "artifact" instead. But I think potentially TaskState could be a good name for a stateful tasks framework, and if we called this enum something like TaskRunState or TaskExecutionState -- or perhaps more accurately TaskInstanceExecutionState there would be no conflict. -- 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: us...@infra.apache.org
