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

ASF subversion and git services commented on NIFI-5217:
-------------------------------------------------------

Commit d79216d6b08a842dc0c5f6b847429aae87fb5561 in nifi's branch 
refs/heads/master from [~ca9mbu]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=d79216d ]

NIFI-5217: Allow non-nullable fields to be added to MockRecordParser

Signed-off-by: Matthew Burgess <[email protected]>

This closes #2720


> 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
>             Fix For: 1.7.0
>
>
> 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)

Reply via email to