On Fri, Jun 18, 2010 at 4:57 PM, Miguel Verde <miguelitov...@gmail.com> wrote: > On Fri, Jun 18, 2010 at 6:23 PM, Tatu Saloranta <tsalora...@gmail.com> > wrote: >> >> Not that I wanted to criticize choices, but do they actually allow use >> of JSON as encoding? >> Avro does use JSON for specifying schemas, but I wasn't aware of being >> able to use it for encoding data. >> Likewise with Thrift. > > Yes, each supports a JSON data encoding. See > http://avro.apache.org/docs/1.3.3/spec.html#json_encoding for Avro and the > JSONProtocol in Thrift. One clear advantage of these two is that they
Ok thanks. I learnt something new today. :-) > support either stringified JSON or a compact binary encoding, and that they > each support (or intend to support) a more efficient TCP-based protocol > instead of only allowing HTTP. Right. Latter is actually useful, then, as that would suggest possibility of using alternative binary encodings with other pieces (schema definition, protocol handling).... (encoding that supports their respective data sets) > Re: Avro vs Thrift, Cassandra has historically had difficulty getting Thrift > bugs fixed and Avro is more malleable at this point. Additionally, Avro has > the potential for a more compact encoding and easier integration with > dynamic languages. Yes, that has been my impression as well, so I was not surprised to see plans for this change. Although I have been interested in learning more about progress, to know when would new versions be available. -+ Tatu +-
