Hi, Is the intent for logical types to all be specified as part of the Avro spec, or should users be able to add custom types? If users can add custom types, any thoughts on naming conventions to avoid conflicts with future types added to the spec?
Specifically, I want to support unsigned longs in internal applications. That would seem to be a good fit for a custom logical type, the alternative being adding a custom attribute to trigger additional decoding logic on top of fixed bytes. Thanks, Justin
