One of the challenges that we have at LinkedIn is that we have a *lot* of
Avro schemas. I'd like to be able to represent those Avro schemas using
Iceberg's types and there are a few challenges:
- unions
- enums
- default values
One way out of those problems without extending the Iceberg type model is
to add type attributes where each sub-type has a logical string to string
map that can hold user-defined attributes.
Another use for those kind of attributes are to mark columns with
classification tags (eg. pii, etc.).
Thoughts,
Owen
