[
https://issues.apache.org/jira/browse/FLINK-9586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-9586:
----------------------------------
Labels: Collections auto-deprioritized-major auto-deprioritized-minor
parallel (was: Collections auto-deprioritized-major parallel stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> Make collection sources parallelisable
> --------------------------------------
>
> Key: FLINK-9586
> URL: https://issues.apache.org/jira/browse/FLINK-9586
> Project: Flink
> Issue Type: Improvement
> Components: API / DataSet
> Affects Versions: 1.5.0
> Reporter: Sina Madani
> Priority: Not a Priority
> Labels: Collections, auto-deprioritized-major,
> auto-deprioritized-minor, parallel
>
> The note in
> [https://ci.apache.org/projects/flink/flink-docs-release-1.5/dev/datastream_api.html#collection-data-sources]
> states that Collecitons are mainly there for testing and do not support
> parallelism. I believe this to be an unnecessary assumption - I'm sure there
> are plenty of use cases that already have the data they need to distribute
> ready at hand. It seems strange that a fixed collection of inputs cannot be
> parallelised by Flink, which would require users to write their Collections
> into a text file and re-read them just to get parallelisation.
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
