You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/06/02 23:30:02 UTC

[jira] [Updated] (FLINK-16735) FlinkKafkaProducer should check that it is not null before sending a record

     [ https://issues.apache.org/jira/browse/FLINK-16735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flink Jira Bot updated FLINK-16735:
-----------------------------------
    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.


> FlinkKafkaProducer should check that it is not null before sending a record
> ---------------------------------------------------------------------------
>
>                 Key: FLINK-16735
>                 URL: https://issues.apache.org/jira/browse/FLINK-16735
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka
>    Affects Versions: 1.10.0
>            Reporter: Shangwen Tang
>            Priority: Major
>              Labels: auto-unassigned, stale-major
>         Attachments: image-2020-03-24-11-40-22-143.png
>
>
> In our user scenario, some users implemented the KafkaSerializationSchema and sometimes returned a null record, resulting in a null pointer exception
> !image-2020-03-24-11-40-22-143.png!



--
This message was sent by Atlassian Jira
(v8.3.4#803005)