avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryan Blue (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AVRO-1792) Cannot specify a 'null' default value
Date Wed, 03 Feb 2016 18:51:39 GMT

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

Ryan Blue commented on AVRO-1792:
---------------------------------

[~kpriceyahoo], I thought that using JsonProperties.NULL_VALUE worked. Can you post a test
case that demonstrates where this fails?

> Cannot specify a 'null' default value
> -------------------------------------
>
>                 Key: AVRO-1792
>                 URL: https://issues.apache.org/jira/browse/AVRO-1792
>             Project: Avro
>          Issue Type: Bug
>          Components: java
>    Affects Versions: 1.8.0
>            Reporter: Kevin J. Price
>            Priority: Minor
>
> Using the new Schema.Field constructors added in 1.8.0, it is no longer possible to use
the Java API to construct a schema field with a 'null' default value. That is, the following
schema cannot be constructed without using the deprecated API:
> {code}
> {
> 	"type": "record",
> 	"name": "base",
> 	"fields": [{
> 		"name": "a",
> 		"type": ["null", "string"],
> 		"default": null
> 	}]
> }
> {code}
> This is because passing a "null" value to the new API implies no default. Passing the
"JsonProperties.NULL_VALUE" sentinel value doesn't work either, because when it is parsed
by "JacksonUtils.toJsonNode", it turns into "null".



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message