You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@kafka.apache.org by "Guozhang Wang (JIRA)" <ji...@apache.org> on 2018/06/04 05:43:00 UTC

[jira] [Resolved] (KAFKA-5058) Add a sensor to KafkaStreams to track records that have been dropped due to having a null key

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

Guozhang Wang resolved KAFKA-5058.
----------------------------------
       Resolution: Fixed
         Assignee: John Roesler
    Fix Version/s: 2.0.0

This has been resolved in https://cwiki.apache.org/confluence/display/KAFKA/KIP-274%3A+Kafka+Streams+Skipped+Records+Metrics, coming in 2.0

> Add a sensor to KafkaStreams to track records that have been dropped due to having a null key
> ---------------------------------------------------------------------------------------------
>
>                 Key: KAFKA-5058
>                 URL: https://issues.apache.org/jira/browse/KAFKA-5058
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 0.10.2.0
>            Reporter: Damian Guy
>            Assignee: John Roesler
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> In various places, i.e., {{KTableSource}}, {{StoreChangelogReader}}, {{KStreamWindowAggregate}} etc, we drop records with a null key. We probably should consider creating a sensor to track records that have been dropped.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)