Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3113
Given that this only extends the enum and does not add changes to the state
transitions, we can merge this.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user wangzhijiang999 commented on the issue:
https://github.com/apache/flink/pull/3113
@StephanEwen , I already created #5703 for further detail recovery process
and it may cover your considerations. Wish your further response, thank you!
---
If your project is set up for it,
Github user wangzhijiang999 commented on the issue:
https://github.com/apache/flink/pull/3113
@StephanEwen , thank you for the concrete suggestions. Sorry for delay
response because of Chinese Spring Festival Holiday.
I have considered and added some tests to validate the stat
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3113
Considering the possible state transitions:
## ExecutionState
- `RECONCILING` can only be entered from `CREATED`
Simple:
- `RECONCILING` can go to `RUNNING` if the tas
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3113
Will merge this.
To make it proper robust, I will add some tests that validate the state
transitions of the state machine...
---
If your project is set up for it, you can reply to this email
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3113
I would like to take a look at this soon...
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Github user uce commented on the issue:
https://github.com/apache/flink/pull/3113
Thanks for the PR. This looks good to me. I'm not too familiar with the
FLIP-6 plans though. I would wait for someone who is in on that to merge this.
---
If your project is set up for it, you can reply
