nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mohit" <>
Subject RE: Validate Record issue
Date Wed, 02 May 2018 17:38:53 GMT
Hi Mark,


I set the Strict type checking to false, still it doesn’t allowed.





From: Mark Payne <> 
Sent: 02 May 2018 23:00
Subject: Re: Validate Record issue




If you look at the Provenance events that are emitted by the processor, they show the reason
that the records

are considered invalid. Specifically, for this use case, it shows: The following 2 fields
had values whose type did not match the schema: [/hs_kbps, /site_id]

It appears that in your incoming data, the values are integers, instead of doubles. If you
have the "Strict Type Checking"

value set to "false" in the processor, then it should allow this. Unfortunately, though, it
appears that there is a bug

that causes integer values not to be considered validate when the schema says that it is a
double. I created a JIRA [1] for this.


In the meantime, if you update your schema to allow for those fields to be ["null", "long",
"double"] then you should be good.







On May 2, 2018, at 11:57 AM, Mohit < <>
> wrote:



I’m using ValidateRecord processor to validate CSV and writing to avro. 

For a file it is transferring all the record to an invalid relationship. It is working fine
with ConvertCsvToAvro processor.


Avro Schema - {"type":"record","name":"cell_kpi_dump_geo","namespace":"cell_kpi_dump_geo","fields":[{"name":"month","type":["null","string"],"default":null},






Sample record – 




Is there something I’m doing wrong?






View raw message