[
https://issues.apache.org/jira/browse/NIFI-4579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Lim updated NIFI-4579:
-----------------------------
Description:
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.
was:
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.
> 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
>
> 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
(v6.4.14#64029)
