[jira] [Commented] (NIFI-4579) When Strict Type Checking property is set to "false", ValidateRecord does not coerce fields into the correct type.

["Koji Kawamura (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16511936#comment-16511936 ] 

Koji Kawamura commented on NIFI-4579:
-------------------------------------

[~andrewmlim] Thanks for reporting this. I stumble upon the same behavior today. I think the documentation is right and the implementation needs to be fixed. By looking at the source code, ValidateRecord processor uses the input schema to write 'valid' records regardless of the writer's configuration.

I'm testing a fix locally and will send a PR shortly.

> When Strict Type Checking property is set to "false", ValidateRecord does not coerce fields into the correct type.
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: NIFI-4579
>                 URL: https://issues.apache.org/jira/browse/NIFI-4579
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Documentation & Website, Extensions
>    Affects Versions: 1.4.0
>            Reporter: Andrew Lim
>            Assignee: Koji Kawamura
>            Priority: Major
>
> The description of the Strict Type Checking property for the ValidateRecord processor states:
> _If false, the Record will be considered valid and the field will be coerced into the correct type (if possible, according to the type coercion supported by the Record Writer)._
> In my testing I've confirmed that in this scenario, the records are considered valid.  But, none of the record fields are coerced into the correct type.
> We should either correct the documentation or implement the promised coercion functionality.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)