[
https://issues.apache.org/jira/browse/FLINK-9058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467323#comment-16467323
]
ASF GitHub Bot commented on FLINK-9058:
---------------------------------------
Github user StefanRRichter commented on the issue:
https://github.com/apache/flink/pull/5749
What exactly is the benefit of this change? Or why `Iterable` and not
`Collection` so that we can benefit from methods like `addAll(...)` which can
optimize insertion because the size is known.
> Relax ListState.addAll() and ListState.update() to take Iterable
> ----------------------------------------------------------------
>
> Key: FLINK-9058
> URL: https://issues.apache.org/jira/browse/FLINK-9058
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Reporter: Aljoscha Krettek
> Assignee: Aljoscha Krettek
> Priority: Major
> Fix For: 1.5.0
>
>
> [~srichter] What do you think about this. None of the implementations require
> the parameter to actually be a list and allowing an {{Iterable}} there allows
> calling it in situations where all you have is an {{Iterable}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
