[jira] [Resolved] (KAFKA-7015) Enhance RecordCollectorImpl exceptions with more context information

["Matthias J. Sax (Jira)" <ji...@apache.org>]

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

Matthias J. Sax resolved KAFKA-7015.
------------------------------------
    Resolution: Not A Problem

We should actually not log sensitive information like key and value and actually removed some log statements that may leak key/value information. Hence, closing this ticket.

> Enhance RecordCollectorImpl exceptions with more context information	
> ---------------------------------------------------------------------
>
>                 Key: KAFKA-7015
>                 URL: https://issues.apache.org/jira/browse/KAFKA-7015
>             Project: Kafka
>          Issue Type: Improvement
>          Components: streams
>    Affects Versions: 1.1.0
>            Reporter: Matthias J. Sax
>            Priority: Minor
>
> In KIP-182 we refactored all stores to by plain {{Bytes/byte[]}} stores and only have concrete key/value types on outer layers/wrappers of the stores.
> For this reason, the most inner {{RocksDBStore}} cannot provide useful error messages anymore if a put/get/delete operation fails as it only handles plain bytes.
> In addition, the corresponding calls to record changelog records to record collectors will also be sending byte arrays only, and hence when there is an error happening, the record collector can only display the key but not the value since it is all bytes:
> {code:java}
> [ERROR] org.apache.kafka.streams.processor.internals.RecordCollectorImpl   -
> task [2_2] Error sending record (key {"eventId":XXX,"version":123}
> value [<byte array>] timestamp YYY) to topic TTT
> due to ...
> {code}
> The store exceptions got fixed via KAFKA-6538.
> This Jira is to track the fix for RecordCollectorImpl.



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