You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Daniel Kulp (JIRA)" <ji...@apache.org> on 2019/04/05 12:55:00 UTC
[jira] [Resolved] (AVRO-2368) Provide way to distinguish whether a
Schema.Field has a default value or its default is null
[ https://issues.apache.org/jira/browse/AVRO-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Daniel Kulp resolved AVRO-2368.
-------------------------------
Resolution: Fixed
Assignee: Daniel Kulp
Field.hasDefaultValue() method added.
> Provide way to distinguish whether a Schema.Field has a default value or its default is null
> --------------------------------------------------------------------------------------------
>
> Key: AVRO-2368
> URL: https://issues.apache.org/jira/browse/AVRO-2368
> Project: Apache Avro
> Issue Type: Task
> Components: java
> Reporter: Ivan Greene
> Assignee: Daniel Kulp
> Priority: Blocker
> Fix For: 1.9.0
>
>
> After making {{Schema.Field#defaultValue}} package private, there is no way to distinguish whether a Field has a default value of 'null' or has no default at all. This is a breaking change, notably affecting Hortonworks Schema Registry. See discussion here: [https://github.com/hortonworks/registry/pull/547]
> I propose we should make that method public and still deprecated. Otherwise I don't see a clear way to release a version of the Hortonworks registry that will be compatible with both Avro 1.8.x and 1.9.0.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)