You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Benchao Li (Jira)" <ji...@apache.org> on 2020/03/28 03:23:00 UTC
[jira] [Commented] (FLINK-16827) Kafka stream data sorted by time
field throws null pointer exception under multiple concurrency
[ https://issues.apache.org/jira/browse/FLINK-16827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069206#comment-17069206 ]
Benchao Li commented on FLINK-16827:
------------------------------------
[~robinjun] Yes, you are right, we've spotted this bug too. It's because in `StreamExecTemporalSortRule`, we didn't add `FlinkRelDistribution`.
> Kafka stream data sorted by time field throws null pointer exception under multiple concurrency
> -----------------------------------------------------------------------------------------------
>
> Key: FLINK-16827
> URL: https://issues.apache.org/jira/browse/FLINK-16827
> Project: Flink
> Issue Type: Bug
> Components: API / Core
> Affects Versions: 1.9.1
> Environment: flink on yarn
> !image-2020-03-27-21-23-13-648.png!
> Reporter: wuchangjun
> Priority: Major
> Attachments: image-2020-03-27-21-22-21-122.png, image-2020-03-27-21-22-44-191.png, image-2020-03-27-21-23-13-648.png
>
>
> flink reads kafka data and sorts by time field. In the case of multiple concurrency, it throws the following null pointer exception. One concurrent processing is normal.
> !image-2020-03-27-21-22-21-122.png!
>
> !image-2020-03-27-21-22-44-191.png!
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)