Github user tzulitai commented on the issue:
https://github.com/apache/flink/pull/4301
@StephanEwen
Regarding no-rediscover on restore test:
yes, could say that it is covered in
`KafkaConsumerTestBase.runMultipleSourcesOnePartitionExactlyOnceTest()`. It's
an end-to-end exactly-once test for the case where Flink source subtask count >
partition count.
Regarding `ListState`:
The redistribution of `ListState` doesn't conflict with discovery and
assignment of partitions in the `release-1.3` case (where there is no partition
discovery), because we don't respect the partition assignment logic if we're
starting from savepoints. We only consider what's in the restored state. See
also @aljoscha's comment above.
For `master` where partition discovery is already merged, the `ListState`
is a union list state, where all subtasks are broadcasted with all partition
states. On restore, the restored union list state is filtered again with the
assignment logic.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
