[
https://issues.apache.org/jira/browse/AVRO-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Dickson updated AVRO-4026:
-------------------------------
Description:
AVRO-3601 fixed the install issue, but any schema with non-string custom
attributes now fails to compile with an exception.
For example the following schema that cannot be compiled in 1.11.2, while it
worked in earlier versions:
{code}
{
"type": "record",
"name": "Test",
"fields": [ {
"name": "f1",
"type": "string",
"extra": {
"custom1": "value",
"custom2": true
}
} ]
}
{code}
was:
AVRO-3601 fixed the install issue, but any schema with non-string custom
attributes now fails to compile with an exception.
For example the following schema that cannot be compiled in 1.11.2, while it
worked in earlier versions:
{{{}}
{{ "type": "record",}}
{{ "name": "Test",}}
{{ "fields": [ {}}
{{ "name": "f1",}}
{{ "type": "string",}}
{{ "extra": {}}
{{ "custom1": "value",}}
{{ "custom2": true}}
{{ }}{{}}}
{{ }}{{} ]}}
{{}}}
> Schemas with non-string custom attributes fail to compile
> ---------------------------------------------------------
>
> Key: AVRO-4026
> URL: https://issues.apache.org/jira/browse/AVRO-4026
> Project: Apache Avro
> Issue Type: Bug
> Components: c++
> Affects Versions: 1.11.2, 1.11.3
> Reporter: John Dickson
> Priority: Major
> Labels: pull-request-available
> Time Spent: 40m
> Remaining Estimate: 0h
>
> AVRO-3601 fixed the install issue, but any schema with non-string custom
> attributes now fails to compile with an exception.
> For example the following schema that cannot be compiled in 1.11.2, while it
> worked in earlier versions:
> {code}
> {
> "type": "record",
> "name": "Test",
> "fields": [ {
> "name": "f1",
> "type": "string",
> "extra": {
> "custom1": "value",
> "custom2": true
> }
> } ]
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
