Github user wangzhijiang999 commented on the issue:
https://github.com/apache/flink/pull/3125
@StephanEwen
Yes, the current concern is only focusing on state restore performance.
This PR does not consider all the scenarios and it may be only the first step
for the slot location implementation.
If the location do not exist, it can add other strategies to decide the
locations, such as co-loated by input for batch job as you mentioned. And it
can be the second step for the implementation.
Wish your further comments!
---
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 feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
