[
https://issues.apache.org/jira/browse/AVRO-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17373766#comment-17373766
]
ASF subversion and git services commented on AVRO-3144:
-------------------------------------------------------
Commit 8dd55dbac12103c4e81be199a7d819e8e8fb5b56 in avro's branch
refs/heads/master from Andreas Hailu
[ https://gitbox.apache.org/repos/asf?p=avro.git;h=8dd55db ]
AVRO-3144 Support for enabling and disabling default value validation through
SchemaBuilder (#1276)
* AVRO-3144 Support for enabling and disabling default value validation through
SchemaBuilder
* AVRO-3144 Fix spotless violations
> SchemaBuilder: Support making validation of default values configurable
> -----------------------------------------------------------------------
>
> Key: AVRO-3144
> URL: https://issues.apache.org/jira/browse/AVRO-3144
> Project: Apache Avro
> Issue Type: Improvement
> Reporter: Andreas Hailu
> Assignee: Andreas Hailu
> Priority: Major
>
> The SchemaBuilder's createFields methods pass a value of 'true' to the
> validateDefault option within the Field constructor.
> While this is very useful to have, it results in not being able to seamlessly
> migrate from 1.8 to >= 1.9 if an application/registry already has schemata
> with invalid defaults.
> Given that Schema.Parser allows us to configure this, can we support the same
> idea within SchemaBuilder?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
