This is similar to https://issues.apache.org/jira/browse/AVRO-4026 which has a PR here https://github.com/apache/avro/pull/3069. This PR only supports custom attributes on fields, it doesn't address Arrays though.
1.11.0 and 1.11.1 fully supported custom attributes on fields, but the installer didn't include the headers needed for release. https://issues.apache.org/jira/browse/AVRO-3601 fixed this but some developers felt the built-in JSON DOM wasn't in a state to be exposed, so it removed support for non-string attributes on fields. To keep with this, PR 3069 exopses custom attributes as JSON strings so the end user can use the JSON parser of their choosing to interact with their values. On Fri, Sep 20, 2024 at 4:42 AM Pascal Ginter (Jira) <j...@apache.org> wrote: > Pascal Ginter created AVRO-4058: > ----------------------------------- > > Summary: Issue in schema preservation > Key: AVRO-4058 > URL: https://issues.apache.org/jira/browse/AVRO-4058 > Project: Apache Avro > Issue Type: Bug > Reporter: Pascal Ginter > > > While trying to write an [Iceberg Manifest List File|[ > https://iceberg.apache.org/spec/#manifest-lists],] 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 a PR (at least for > the first point 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. > > > > -- > This message was sent by Atlassian Jira > (v8.20.10#820010) >
