[
https://issues.apache.org/jira/browse/NIFI-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007832#comment-18007832
]
David Handermann commented on NIFI-14756:
-----------------------------------------
Thanks for the additional background [~awelless], and thanks for the
perspective on options [~pvillard].
Given the initial goal of manual troubleshooting, I think it would be better
for the initial approach to add debug logging. FlowFile attributes use memory,
and a large number of long attributes can create compounding problems. There
may still be value in some type of abstracted error code, as mentioned, not
exposing the Java class, but a reference.
With that background, I recommend going with a debug log to start with, and if
other reasons come up for adding attributes, those can be considered.
> Log error when a parsing error occurs in ConsumeKafka
> -----------------------------------------------------
>
> Key: NIFI-14756
> URL: https://issues.apache.org/jira/browse/NIFI-14756
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Minor
>
> When a parsing error occurs, a record is sent to parse.failure, without any
> error message.
> To make troubleshooting easier, the error message should be added to flow
> file properties.
> Code pointer:
> [https://github.com/apache/nifi/blob/main/nifi-extension-bundles/nifi-kafka-bundle/nifi-kafka-processors/src/main/java/org/apache/nifi/kafka/processors/consumer/convert/AbstractRecordStreamKafkaMessageConverter.java#L113]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
