[ https://issues.apache.org/jira/browse/AVRO-680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sachin Goyal updated AVRO-680: ------------------------------ Attachment: avro_circular_refs6.patch avro_circular_refs6.patch is created using {code} lang/java/avro% svn diff src/ {code} It eliminates the need to add an extra field per record and relies on the order of record-writing and reading. In this patch, there is an equals check at 3 places of the form: {code:java} schema.getFullName().equals(CircularRef.class.getName()) {code} I think this could be improved by adding a boolean-property in the schema for CircularRef or somehow comparing the class. Comments are welcome. > Allow for non-string keys > ------------------------- > > Key: AVRO-680 > URL: https://issues.apache.org/jira/browse/AVRO-680 > Project: Avro > Issue Type: Improvement > Affects Versions: 1.7.6, 1.7.7 > Reporter: Jeremy Hanna > Attachments: AVRO-680.patch, avro_circular_refs6.patch, > isMap_Call_Hierarchy.png, non_string_map_keys.zip, non_string_map_keys2.zip, > non_string_map_keys3.zip, non_string_map_keys4.patch, > non_string_map_keys5.patch, non_string_map_keys6.patch, > non_string_map_keys7.patch > > > Based on an email thread back in April, Doug Cutting proposed a possible > solution for having non-string keys: > Stu Hood wrote: > > I can understand the reasoning behind AVRO-9, but now I need to look for an > > alternative to a 'map' that will allow me to store an association of bytes > > keys to values. > A map of Foo has the same binary format as an array of records, each > with a string field and a Foo field. So an application can use an array > schema similar to this to represent map-like structures with, e.g., > non-string keys. > Perhaps we could establish standard properties that indicate that a > given array of records should be represented in a map-like way if > possible? E.g.,: > {"type": "array", "isMap": true, "items": {"type":"record", ...}} > Doug -- This message was sent by Atlassian JIRA (v6.2#6252)