[
https://issues.apache.org/jira/browse/NIFI-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16481117#comment-16481117
]
ASF GitHub Bot commented on NIFI-5217:
--------------------------------------
Github user mattyb149 commented on the issue:
https://github.com/apache/nifi/pull/2720
The Travis failure was on one build because of a port conflict, the others
pass (with contrib-check). Merging to master, thanks!
> Allow MockRecordParser to add non-nullable fields
> -------------------------------------------------
>
> Key: NIFI-5217
> URL: https://issues.apache.org/jira/browse/NIFI-5217
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Matt Burgess
> Assignee: Matt Burgess
> Priority: Major
>
> MockRecordParser (in nifi-mock-record-utils) has an addSchemaField() method,
> but it does not have a parameter to set whether the field is nullable or not.
> Thus it creates a new RecordField without the nullable parameter, in which
> case it defaults to "true". This prevents tests from adding a non-nullable
> field.
> This Jira proposes to overload addSchemaField() with a boolean "isNullable"
> parameter that will be passed along to the RecordField constructor.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
