[
https://issues.apache.org/jira/browse/FLINK-2284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-2284:
----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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.
> Confusing/inconsistent PartitioningStrategy
> -------------------------------------------
>
> Key: FLINK-2284
> URL: https://issues.apache.org/jira/browse/FLINK-2284
> Project: Flink
> Issue Type: Bug
> Components: API / DataStream
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> The PartitioningStrategy in
> {{org.apache.flink.streaming.runtime.partitioner.StreamPartitioner.java}} is
> non standard and not easily understandable.
> What form of partitioning is `SHUFFLE`? Shuffle just means "redistribute", it
> says nothing about what it does. Same with `DISTRIBUTE`. Also `GLOBAL` is not
> a well-defined/established term. Why is `GROUPBY` a partition type? Doesn't
> grouping simply hash partition (like I assume "SHUFFLE" means), so why does
> it have an extra entry?
> Sticking with principled and established names/concepts is important to allow
> people to collaborate on the code.
> Why not stick with the partitioning types defined in the batch API? They are
> well defined and named:
> ```
> NONE, FORWARD, RANDOM, HASH, RANGE, FORCED_REBALANCE, BROADCAST, CUSTOM
> ```
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
