[
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 parallel stale-minor (was:
Collections auto-deprioritized-major parallel)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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: Minor
> Labels: Collections, auto-deprioritized-major, parallel,
> stale-minor
>
> 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)
