Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Plain View
Avro >> mail # user >> Limitations in enum symbols not mentioned in the spec


+
Francis Galiegue 2013-02-27, 16:24
+
Francis Galiegue 2013-02-27, 16:27
+
Doug Cutting 2013-02-27, 17:55
+
Francis Galiegue 2013-02-27, 18:12
+
Doug Cutting 2013-02-27, 18:40
+
Francis Galiegue 2013-02-27, 18:43
+
Tatu Saloranta 2013-02-27, 18:53
+
Francis Galiegue 2013-02-27, 19:10
+
Tatu Saloranta 2013-02-28, 06:41
Copy link to this message
-
Re: Limitations in enum symbols not mentioned in the spec
On Wed, Feb 27, 2013 at 10:43 AM, Francis Galiegue <[EMAIL PROTECTED]> wrote:
> I was talking about what is allowed in map keys, not values

So was I.

> if map
> keys were able to be anything other than strings, Avro could not be
> mapped to JSON.

Yes, JavaScript is an example of a programming language whose standard
map implementation doesn't provide support for non-string keys.
JavaScript however is not an example of a programming language whose
identifiers permit a only a limited set of characters, since (I
believe) one can escape arbitrary characters in property accessors
when using the dot syntax.

Doug
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB