incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Courtney Robinson" <>
Subject Re: Cassandra for graph data structure
Date Mon, 27 Sep 2010 06:37:08 GMT
´╗┐Efficient, i'm not totally sure on yet. Would need to do some testing.
A quick mock up should highlight any tradeoffs being made.
I think its been decided we'll test it out by creating a simple client using 
and if results look good we'll have an attempt using hector as a layer.

From: "Ran Tavory" <>
Sent: Saturday, September 25, 2010 1:41 PM
To: <>
Subject: Re: Cassandra for graph data structure

> Courtney this certainly sounds interesting and as Nate suggested we're
> always looking for valuable contributions.
> A few things to keep in mind:
> - I'm curious, as Lucas has asked - is it possible to create an
> efficient graph API over cassandra and what are the tradeoffs?
> - If the API is general enough and the functionality is reusable then
> we'd be happy to add it to hector. If not, you can create a library
> that uses hector as a layer.
> On Friday, September 24, 2010, Courtney Robinson <> wrote:
>> ?Nate & Lucas thanks for the responses.
>> Nate, I think it would be asking a bit much to suggest the hector team 
>> implement convenience methods for
>> a graph representations. But if we went ahead and forked hector, I'd be 
>> sure to contribute back what i can and just release it as another client
>> or if the final product can be merged with hector...
>> I'd like thoughts on any features outside my own usecase though so that 
>> we can build it to handle other use cases as well.
>> Lucas, I understand what you're saying but i've had a quick play with 
>> neo4j and the expense we'd pay for reads offsets a lot of the
>> setbacks i'd run into using neo4j, not to mention having to learn it...
>> --------------------------------------------------
>> From: "Nate McCall" <>
>> Sent: Friday, September 24, 2010 4:14 PM
>> To: <>
>> Subject: Re: Cassandra for graph data structure
>> My idea however was to fork hector, remove all the stuff i don't need and
>> turn it into a graph API sitting on top of Cassandra.
>> We are always looking for ideas and design feedback regarding Hector.
>> Please feel free to make suggestions or fork and send pull requests.

View raw message