Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of tsaloranta@gmail.com
 designates 209.85.211.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=HX8pV9/fH13/Z1sP7Ll01TAYscCTLFEHmocx4OiqnQ+oa5uR55LsjVU0FlxmjJ7AUA
         ljYpS7CsN3oc1R4Wv1WZG5rhHYvqJbHR3KUzEvV99LlcEsHsdkbnuOKgzNYBoI8hI4MG
         9iZ+KSVaNwv3y1pTqmIDeYT1wJP5bGxQD+IYc=
MIME-Version: 1.0
In-Reply-To: <AANLkTil0-BeyEAdR66pSOno2lz8BNTIu88D8m6aWMwF4@mail.gmail.com>
References: <AANLkTikcDrne2A0QHkpj7MZJq5zjklWzWhTSRnTVnCtY@mail.gmail.com>
	<1276873264.3832.26.camel@erebus.lan>
	<9C7A4E39-F8D2-49C3-BCE2-C9C75431979D@gmail.com>
	<1276895545.3832.78.camel@erebus.lan>
	<AANLkTimXXzSsl5Yp8Aetwar11IT2G6oWoAAI4MdcVydZ@mail.gmail.com>
	<AANLkTil0-BeyEAdR66pSOno2lz8BNTIu88D8m6aWMwF4@mail.gmail.com>
Date: Fri, 18 Jun 2010 17:07:03 -0700
Message-ID: <AANLkTim_JMCXBi1Nl-9J-oGkhGlqyWfKnwrVGmKVzB59@mail.gmail.com>
Subject: Re: AVRO client API
From: Tatu Saloranta <tsaloranta@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Fri, Jun 18, 2010 at 4:57 PM, Miguel Verde <miguelitovert@gmail.com> wro=
te:
> On Fri, Jun 18, 2010 at 6:23 PM, Tatu Saloranta <tsaloranta@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.=A0 See
> http://avro.apache.org/docs/1.3.3/spec.html#json_encoding=A0for Avro and =
the
> JSONProtocol in Thrift.=A0 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 th=
ey
> 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 Thr=
ift
> bugs fixed and Avro is more malleable at this point.=A0 Additionally, Avr=
o 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 +-