[ https://issues.apache.org/jira/browse/KAFKA-7015?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575212#comment-16575212 ]
John Roesler commented on KAFKA-7015: ------------------------------------- It's probably good to avoid displaying the values in error messages anyway, as it can be a security issue. Nevertheless, it would be nice to display the keys. > 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 > Assignee: Jagadesh Adireddi > 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 (v7.6.3#76005)