[
https://issues.apache.org/jira/browse/NIFI-5264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16503189#comment-16503189
]
bsf commented on NIFI-5264:
---------------------------
Hey [~pvillard],
Thanks for your suggestion.
We have some big and large CSV files for validation, and often the invalid flow
result is big and large as well.
We need to go and fix things in the invalid flow file but It's very hard and
long without an error message per line.
The idea of a "validation.error.message" attribute is super nice if we can
concatenate all the error messages raised during the validation with the line
number in that attribute. In other words the attribute will become more like a
"validation.error.report"
Something like :
{code}
validation.error.report :
line 145323: 107/02/15 is not a valid date
line 348890: "Am a field and I should be numeric" is not numeric
line 366489 : Unknown error
{code}
Thought ?
> Add parsing failure message in ValidateCSV
> -------------------------------------------
>
> Key: NIFI-5264
> URL: https://issues.apache.org/jira/browse/NIFI-5264
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.6.0
> Reporter: bsf
> Assignee: Pierre Villard
> Priority: Major
>
> As a developer I would like to see an improvement on the ValidateCSV
> component when using the line by line validation strategy. It will be nice to
> have an option to append into the flowfile on the invalid relationship 1 or 2
> new fields:
> * field_name : the name of the field failed in the schema validation
> * field_description : the description of the validation error
> This will help a lot the user to understand the validation issue on each line.
> If too complex, anything that provides information on the fail validation of
> the line against the schema will be more than welcome :)
> Pentaho DI do something like this by enabling error handling.
> Thanks a lot!
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
