Github user tweise commented on the issue:
https://github.com/apache/flink/pull/5393
@tzulitai Assignment and restore are orthogonal; this PR doesn't change
restore. I therefore don't see the need to add another migration test for it.
There is also no change to how the index is computed by default, it is just
that part of what happened earlier in `isThisSubtaskShouldSubscribeTo` is now
in the assigner. Should I add a (trivial) unit test that asserts that
`isThisSubtaskShouldSubscribeTo` applies modulus to assigner returned value
that falls outside the subtask index range?
---
