[
https://issues.apache.org/jira/browse/FLINK-16193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16193:
-----------------------------------
Labels: auto-unassigned stale-major (was: auto-unassigned)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Improve error messaging when a key is assigned to the wrong key group range
> ---------------------------------------------------------------------------
>
> Key: FLINK-16193
> URL: https://issues.apache.org/jira/browse/FLINK-16193
> Project: Flink
> Issue Type: Improvement
> Components: API / DataStream
> Affects Versions: 1.11.0
> Reporter: Seth Wiesman
> Priority: Major
> Labels: auto-unassigned, stale-major
>
> Occasionally, users may run into an exception that reads something like:
>
> java.lang.IllegalArgumentException: Key group 45 is not in
> KeyGroupRange{startKeyGroup=0, endKeyGroup=42}
>
> This may be caused by a number of issues including:
> 1) Unstable hash and equals methods on their key objects
> 2) Improper use of DataStreamUtils#reinterpretAsKeyedStream
>
> Key group ranges are a fairly low level detail that most users will be
> unfamiliar with when working with Flink. We should offer more comprehensive
> error messaging that outlines likely causes and solutions.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
