[jira] [Updated] (AVRO-3144) SchemaBuilder: Support making validation of default values configurable

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Updated] (AVRO-3144) SchemaBuilder: Support making validation of default values configurable

Dave Cole (Jira)

     [ https://issues.apache.org/jira/browse/AVRO-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andreas Hailu updated AVRO-3144:
--------------------------------
    Description:
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 as 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?

  was:
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 us not being able to migrate from 1.8 to >= 1.9 as our registry already has schemata with invalid defaults. 

Given that Schema.Parser allows us to configure this, can we support the same idea within SchemaBuilder?


> 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
>            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 as 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)