Hi, I think this is because the C++ version still lacks namespace support,
so it thinks "namespace" is an undefined type.


On Wed, May 11, 2011 at 2:32 PM, Ye, Xiaolu - GMRT-EST
<[email protected]>wrote:

> Hi,
>
> I am trying to generate C++ code for my avro schema file and when run *
> precompile*, then I am getting below error
>
> *"Failed to parse or compile schema: Schema is invalid, due to bad node of
> type symbolic" *
>
> The same schema works for Java and .Net code generators. Can you please let
> me know the root cause of the issue.
>
>
> // Below is the schema.
>
> {"namespace": "com.baml.gmrt.messaging.avro.writer",
>  "protocol" : "writer-compatible",
>  "doc" : "Protocol for writer-compatible",
>
>
>  "types" : [
>      {"name": "Kind", "type": "enum", "symbols": ["FOO","BAZ"]},
>
>      {"name": "MD5", "type": "fixed", "size": 16},
>
>      {"name": "MyRecord", "type": "record",
>       "fields": [
>           {"name": "kind", "type": "Kind", "order": "descending"},
>           {"name": "name", "type": "string", "order": "ignore"},
>           {"name": "longType", "type": "int"},
>           {"name": "floatType", "type": "long"},
>           {"name": "doubleType", "type": "float"},
>           {"name": "extra", "type": "string"},
>           {"name": "hash", "type": "MD5"},
>           {"name": "mapTest", "type": {"type": "map", "values": "Kind"}},
>           {"name": "unionTest1", "type": "string"},
>           {"name": "unionTest2", "type": ["Kind", "null"]},
>           {"name": "arrayTest", "type": {"type": "array", "items": "long"}}
>
>       ]
>      }
>   ],
>
>   "messages" : {
>         "A" :{
>                 "doc" : "test long message",
>                 "request" : [{"name": "event", "type":"MyRecord"}],
>                 "response" : "string"
>         }
>   }
> }
>
>
>
> *Thanks,*
>
>
>
> Xiaolu
>
>
> ------------------------------
> This message w/attachments (message) is intended solely for the use of the
> intended recipient(s) and may contain information that is privileged,
> confidential or proprietary. If you are not an intended recipient, please
> notify the sender, and then please delete and destroy all copies and
> attachments, and be advised that any review or dissemination of, or the
> taking of any action in reliance on, the information contained in or
> attached to this message is prohibited.
> Unless specifically indicated, this message is not an offer to sell or a
> solicitation of any investment products or other financial product or
> service, an official confirmation of any transaction, or an official
> statement of Sender. Subject to applicable law, Sender may intercept,
> monitor, review and retain e-communications (EC) traveling through its
> networks/systems and may produce any such EC to regulators, law enforcement,
> in litigation and as required by law.
> The laws of the country of each sender/recipient may impact the handling of
> EC, and EC may be archived, supervised and produced in countries other than
> the country in which you are located. This message cannot be guaranteed to
> be secure or free of errors or viruses.
>
> References to "Sender" are references to any subsidiary of Bank of America
> Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are
> Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a
> Condition to Any Banking Service or Activity * Are Not Insured by Any
> Federal Government Agency. Attachments that are part of this EC may have
> additional important disclosures and disclaimers, which you should read.
> This message is subject to terms available at the following link:
> http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you
> consent to the foregoing.
>

Reply via email to