[
https://issues.apache.org/jira/browse/AVRO-2368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16810852#comment-16810852
]
Ivan Greene commented on AVRO-2368:
-----------------------------------
[~dkulp] are you entirely opposed to exposing the original method again?
WIthout that method I think our only option in Hortonworks is going to be
reflection to create a build that can work with both avro 1.8.2 and 1.9.0
> 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)
