[
https://issues.apache.org/jira/browse/NIFI-14756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18007789#comment-18007789
]
Alaksiej Ščarbaty edited comment on NIFI-14756 at 7/17/25 11:59 AM:
--------------------------------------------------------------------
[~exceptionfactory],
Manual troubleshooting is the goal here. I observed the users often provide
invalid static Avro schema, so the connector fails, but no error is ever
present in the file info as well as logs.
h2. Using an attribute
`record.error.message` is used by Record processors, like `ConvertRecord`,
`RenameRecordField`, `ScriptedPartitionRecord` etc. where an exception message
is used. Is following this pattern not desired in Kafka processors?
h2. Logging an error
This approach will work well for manual debugging. However, I would increase
the level to at least warn, with error being ideal. -Introducing lower logging
levels means a customer has to update NiFi logging levels, which introduces
additional friction.-
was (Author: JIRAUSER308499):
[~exceptionfactory],
Manual troubleshooting is the goal here. I observed the users often provide
invalid static Avro schema, so the connector fails, but no error is ever
present in the file info as well as logs.
h2. Using an attribute
`record.error.message` is used by Record processors, like `ConvertRecord`,
`RenameRecordField`, `ScriptedPartitionRecord` etc. where an exception message
is used. Is following this pattern not desired in Kafka processors?
h2. Logging an error
This approach will work well for manual debugging. However, I would increase
the level to at least warn, with error being ideal. Introducing lower logging
levels means a customer has to update NiFi logging levels, which introduces
additional friction.
> 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)
