[
https://issues.apache.org/jira/browse/AVRO-4026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17906185#comment-17906185
]
Joshua Humphries commented on AVRO-4026:
----------------------------------------
For a little more context, this issue is a blocker for using the Avro C++
library with Apache Iceberg tables, since [the spec for Avro files used by
Iceberg|https://iceberg.apache.org/spec/#avro:~:text=define%20this%20type.-,Field%20IDs,-Iceberg%20struct%2C%20list]
(including the table's manifest and manifest list files, part of the table
metadata) requires including a "field-id" custom attribute that is a number.
(There are also "element-id", "key-id", and "value-id" attributes in array and
map schema definitions.)
> 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: 2.5h
> 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)
