Hello Avro Devs,

I am looking for clarification in the spec as I am working on a
particular implementation for Avro data reading. Most Avro implementations
serialize/deserialize maps using language specific maps that guarantee one
value per key is written and the last value per key read is returned. There
however is no guidance in the spec on whether that is
necessary/implied/expected.

For my use case, I am deserializing keys and values into lists of each,
without checking for uniqueness, and want to know if this breaks the spec,
or if those who serialize maps without unique keys (presumably outside the
bound of most language implementations) can expect undefined behavior when
reading?

-- 
Jack Klamer

Software Engineer

*he/him*
[email protected]
<https://www.starburst.io/>

Reply via email to