[
https://issues.apache.org/jira/browse/AVRO-4058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17883704#comment-17883704
]
Pascal Ginter commented on AVRO-4058:
-------------------------------------
I agree that the spec is not the most clear.
I would argue that it is definitely a bug given the difference in behavior
between language versions but I yield that it is not 100% clear it is in the
C++ version.
The "support" phrasing is used for other types as well, i.e. Enums. The way I
understand it is that the attributes listed as supported are the ones that avro
uses to interpret the schema, not necessarily the only ones allowed.
The comment regarding default values is a good observation.
> Issue in schema preservation
> ----------------------------
>
> Key: AVRO-4058
> URL: https://issues.apache.org/jira/browse/AVRO-4058
> Project: Apache Avro
> Issue Type: Bug
> Components: c++
> Reporter: Pascal Ginter
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While trying to write an Iceberg Manifest List File, which is essentially an
> Avro File with some custom attributes I ran into a few issues which to the
> best of my knowledge are not present in other language implementations or the
> Avro spec. So far I have encountered these issues with the C++ library
> * Arrays are not capable of having custom attributes
> * Attributes in general have to be strings or null. I.e. integers are not
> supported
> I am willing to address these issues myself by writing PRs for the individual
> issues (at least for the first one I know how to fix it. Please let me know
> if there are already any efforts to fix this or reasons why the encountered
> behavior should be preserved.
>
> Edit: PR for custom attributes in arrays exists already
> [https://github.com/apache/avro/pull/3168]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
