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 etamme@gmail.com designates
 209.85.161.44 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=nGqQJz4CMwm8NhPtmgpt49TWKV0m05KcX51FbXLmgz309nzCsxTnJXyAdqBajHr1Wh
         yknoOpX473eaTeKM/g4O6bUf9nOu7HpAxB6aQR7Rqrmf2NFWX+/uySOHzPQok67f2WqH
         hdkkfkizKwKoIGkFI2bf8funxLZCXWDk5KsOY=
MIME-Version: 1.0
In-Reply-To: <BANLkTimwGAx=1bTKSBr3Z96rzUAGa5inDQ@mail.gmail.com>
References: <BANLkTik8xzF=uWdHp71-Ht=Ns8LZRi-njA@mail.gmail.com>
	<BANLkTik2kRsxmfYr5bAiO_+r8deXQpOqJw@mail.gmail.com>
	<BANLkTimwGAx=1bTKSBr3Z96rzUAGa5inDQ@mail.gmail.com>
Date: Wed, 11 May 2011 12:44:03 -0400
Message-ID: <BANLkTi=K582varHnbYHN2UT8_CBXC6s39g@mail.gmail.com>
Subject: Re: Data types for cross language access
From: Eric tamme <etamme@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

> On Wed, May 11, 2011 at 10:23 AM, Luke Biddell <luke.biddell@gmail.com> w=
rote:
>> I wouldn't mind knowing how other people are approaching this problem to=
o.
>>
>> On 11 May 2011 11:27, Oliver Dungey <oliver.dungey@gmail.com> wrote:
>>> I am currently working on a system with Cassandra that is written purel=
y in
>>> Java. I know our end solution will require other languages to access th=
e
>>> data in Cassandra (Python, C++ etc.). What is the best way to store dat=
a to
>>> ensure I can do this? Should I serialize everything to strings/json/xml
>>> prior to the byte conversion? We currently use the Hector=A0serializer,=
 I
>>> wondered if we should just switch this to something like Jackson/JAXB? =
Any
>>> thoughts very welcome.
>>
>

We have clients that use python and C++.  We just generated thrift
bindings for C++ and use thrift directly - it really is not bad at
all, the cassandra.h file generated defines most all methods that any
higher level API would, it just doesn't have built in pooling, or
reconnect etc.

As far as data formats go - we are capturing data (packets) using
libpcap and storing the raw bytes  (literally the entire raw packet
including ethernet and ip headers) into cassandra which are later read
out by python scripts for ascii display, or conversion to pcap files
to open in wireshark.

-Eric