[
https://issues.apache.org/jira/browse/NIFI-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007597#comment-18007597
]
David Handermann commented on NIFI-14756:
-----------------------------------------
[~awelless] Adding the exception message directly may not be the best approach
given the variety of reasons for parsing failures. One option to consider is an
enumeration of error types, mapped from exception classes, but not using the
exception class itself.
On the other hand, logging at the debug level is another option. This could
generate a lot of log messages if there are many records that result in the
same failure, but logging at the debug level is one approach that makes this
optional for troubleshooting.
The best solution depends on whether this change should support manual
troubleshooting using logs, or automated processing, using FlowFile attributes.
Do you have a particular scenario?
> 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: Bug
> Components: Extensions
> Reporter: Alaksiej Ščarbaty
> Assignee: Alaksiej Ščarbaty
> Priority: Major
>
> 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)
