avro-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Longton, Nigel" <Nigel.Long...@pimco.com>
Subject Question about the state of the AVRO C# (csharp) implementation
Date Thu, 13 Mar 2014 14:34:08 GMT
Are there plans to make C# feature equivalent? The major differences seem to be:

1.       C# doesn't  support the Avro IDL schema definition

2.       C# doesn't support the JSON serialization codec

3.       We had a case where we wanted to deserialize a json array which we can do in Java
with Schema.createArray. The equivalent construct in C# was private and so not externally

We're making extensive use of Apache avro to communicate between Java and C# applications
using JSON serialization rather than binary and in some cases we are creating schemas to match
non-avro generated json from 'legacy' applications. I copied the Java json codec to C# and
have got it working (I wont claim its fully tested though). More than happy to post this somewhere
if  its useful.
The other tweak we made was to change how 'default' values were serialized. We created a new
writer classes that if the field value equaled the default it didn't serialize it, and a new
reader class that set missing fields to the schema default if defined (missing non-defaulted
fields are still an error). The advantage is that the JSON created is much cleaner and can
be readily consumed by a jackson or any other json framework. (Currently these aren't ported
to C# due to lack of time).

Are any of the above already scheduled to be added. Some of them might be contra to the avro
approach though.


This message contains confidential information and is intended only for the individual named.
If you are not the named addressee, you should not disseminate, distribute, alter or copy
this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail
by mistake and delete this e-mail from your system. E-mail transmissions cannot be guaranteed
to be secure or without error as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender, therefore, does not accept liability
for any errors or omissions in the contents of this message which arise during or as a result
of e-mail transmission. If verification is required, please request a hard-copy version. This
message is provided for information purposes and should not be construed as a solicitation
or offer to buy or sell any securities or related financial instruments in any jurisdiction.
 Securities are offered in the U.S. through PIMCO Investments LLC, distributor and a company

View raw message