[
https://issues.apache.org/jira/browse/NIFI-11077?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Stieglitz updated NIFI-11077:
------------------------------------
Description:
When a RecordReader fails for whatever reason, it would be helpful to include
in the error log message, a record number to help easily identify which record
failed.
My particular use case was when using QueryRecord and ValidateRecord with
CSVReader on a file which was mostly comma delimited except for one line which
was pipe delimited. The error message logged did not include the line number
where the parsing failed. This made it very difficult to identify which record
in the CSV file was causing the CSVReader to fail.
was:
When a RecordReader fails for whatever reason, it would be helpful to include
in the error log message, a record number to help easily identify which record
failed.
My particular use case was when using QueryRecord and ValidateRecord with
CSVReader on a file which has different delimiters than the rest of the file,
the error message logged did not include the line number where the parsing
failed. This made it very difficult to identify which record in the CSV file
was causing the CSVReader to fail.
> Provide a record number in a error log message when a RecordReader fails
> ------------------------------------------------------------------------
>
> Key: NIFI-11077
> URL: https://issues.apache.org/jira/browse/NIFI-11077
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Daniel Stieglitz
> Priority: Major
>
> When a RecordReader fails for whatever reason, it would be helpful to include
> in the error log message, a record number to help easily identify which
> record failed.
> My particular use case was when using QueryRecord and ValidateRecord with
> CSVReader on a file which was mostly comma delimited except for one line
> which was pipe delimited. The error message logged did not include the line
> number where the parsing failed. This made it very difficult to identify
> which record in the CSV file was causing the CSVReader to fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
