You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/12/13 21:42:00 UTC

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

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

ASF GitHub Bot commented on NIFI-4579:
--------------------------------------

Github user mattyb149 commented on the issue:

    https://github.com/apache/nifi/pull/2794
  
    +1 LGTM, verified the unit test illustrates the behavior and the patch fixes it. Thanks for the fix! Merging to master


> 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 &amp; Website, Extensions
>    Affects Versions: 1.4.0
>            Reporter: Andrew Lim
>            Assignee: Koji Kawamura
>            Priority: Major
>             Fix For: 1.9.0
>
>
> 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)