Github user StefanRRichter commented on the issue:

    https://github.com/apache/flink/pull/4353
  
    I think that idea is problematic because in the rescaling case, all the 
collections can have different sizes. For example there can be 5 managed keyed 
state handles and 7 managed operator state handles and zero state handles for 
the raw state. Then how would you split that up between the 
`OperatorSubtaskStates` in your set? Like this, `OperatorSubtaskState` contains 
the complete state for an operator subtask which I think is a good thing. Also 
maybe at some point there *might* be a reason to report more than one handle 
already on snapshotting.


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

Reply via email to