[ https://issues.apache.org/jira/browse/AVRO-206?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting resolved AVRO-206. ------------------------------- Resolution: Not A Problem Fix Version/s: 1.3.0 Assignee: Patrick Hunt (was: Doug Cutting) This was fixed by AVRO-242, but I've added these tests anyway. > Java compiler/python parser don't conform to spec re object schema > ------------------------------------------------------------------ > > Key: AVRO-206 > URL: https://issues.apache.org/jira/browse/AVRO-206 > Project: Avro > Issue Type: Bug > Components: java, python > Affects Versions: 1.2.0 > Reporter: Patrick Hunt > Assignee: Patrick Hunt > Fix For: 1.3.0 > > Attachments: AVRO-206.patch > > > According to the spec (if I'm reading it correctly) > -- > Primitive type names are also defined type names. Thus, for example, the > schema "string" is equivalent to: > {"type": "string"} > -- protocol > A message has attributes: > * a response schema; and > -- > however the following fails to compile/parse under java/python: > { > "protocol": "p1", > "messages": { > "m1": { > "request": [], > "response": {"type":"string"} > } > } > } > Exception in thread "main" org.apache.avro.SchemaParseException: Type not yet > supported: string > at org.apache.avro.Schema.parse(Schema.java:430) > at org.apache.avro.Protocol.parseMessage(Protocol.java:275) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.