[
https://issues.apache.org/jira/browse/NIFI-4671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16286216#comment-16286216
]
ASF subversion and git services commented on NIFI-4671:
-------------------------------------------------------
Commit f772f2f093de38a97e6a71988628b5fd5aa4139c in nifi's branch
refs/heads/master from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=f772f2f ]
NIFI-4671: This closes #2328. Ensure that Avro Schemas that are created
properly denote fields as being nullable iff the schemas says they are, for
non-top-level fields
Signed-off-by: joewitt <[email protected]>
> When parsing Avro schema, all fields that are not 'top level' are marked as
> nullable
> ------------------------------------------------------------------------------------
>
> Key: NIFI-4671
> URL: https://issues.apache.org/jira/browse/NIFI-4671
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
> Reporter: Mark Payne
> Assignee: Mark Payne
> Fix For: 1.5.0
>
>
> From the mailing list, there is an issue with ValidateRecord considering
> invalid JSON records to be valid when it is missing an 'inner field'. Given
> the following schema:
> {code}
> {
> "name": "aRecord",
> "type": "record",
> "namespace": "a",
> "fields": [
> {
> "name": "a",
> "type": {
> "name": "bRecord",
> "type":"record",
> "fields": [
> { "name": "b", "type": "string"}
> ]
> }
> }
> ]
> }
> {code}
> ValidateRecord will indicate that the following record is valid:
> {code}
> {"a":{}}
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)