Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <4DCAB443.1060107@alex.otherinbox.com>
Date: Wed, 11 May 2011 11:07:31 -0500
From: Alex Araujo <cassandra-users@alex.otherinbox.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Data types for cross language access
References: <BANLkTik8xzF=uWdHp71-Ht=Ns8LZRi-njA@mail.gmail.com>
In-Reply-To: <BANLkTik8xzF=uWdHp71-Ht=Ns8LZRi-njA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 5/11/11 5:27 AM, Oliver Dungey wrote:
> I am currently working on a system with Cassandra that is written 
> purely in Java. I know our end solution will require other languages 
> to access the data in Cassandra (Python, C++ etc.). What is the best 
> way to store data to ensure I can do this? Should I serialize 
> everything to strings/json/xml prior to the byte conversion? We 
> currently use the Hector serializer, I wondered if we should just 
> switch this to something like Jackson/JAXB? Any thoughts very welcome. 
I believe most high level (non-Thrift) clients convert types to/from 
bytes consistently without additional serialization (XML, JSON, etc).  
There may be a few tricks to working with TimeUUIDs for slices, but at 
least the Java and Python versions appear to be compatible. It's 
probably worth writing a few tests using your target languages to make sure:

http://wiki.apache.org/cassandra/ClientOptions

Don't see a C++ client, but a quick Google search turned up:

http://github.com/posulliv/libcassandra