[
https://issues.apache.org/jira/browse/AVRO-680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14069542#comment-14069542
]
Sachin Goyal commented on AVRO-680:
-----------------------------------
Yes, that is correct.
AbstractMap.SimpleEntry does have the private fields "key" and "value".
And AbstractMap is used by number of other classes as shown
[here|http://grepcode.com/search/usages?id=repository.grepcode.com$java$root@jdk$openjdk@6-b14@java$util@AbstractMap&type=type&k=u]
Most maps would seem to work:
#
[TreeMap.Entry|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/util/TreeMap.java#TreeMap.Entry]
#
[LinkedHashMap.Entry|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/util/LinkedHashMap.java#LinkedHashMap.Entry]
and even
#
[ConcurrentHashMap.Entry|http://grepcode.com/file/repository.grepcode.com/java/root/jdk/openjdk/6-b14/java/util/concurrent/ConcurrentHashMap.java#ConcurrentHashMap.HashEntry]
Do you see cases where this can be different, except say really custom-written
Map implementations?
> 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, non_string_map_keys.zip,
> non_string_map_keys2.zip, non_string_map_keys3.zip
>
>
> 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)
