On Feb 22, 2010, at 12:19 AM, ext Jonathan Ellis wrote:
>> 2) is the row key model I suggested above the best approach in Cassandra,
>> or is there something better? My testing so far has been using
>> get_range_slice with a ColumnParent of just the CF and SlicePredicate
>> listing the columns
I'm exploring data layouts and it seems like the common practice is to store an
index in one CF (e.g. userid for row key and thingid for column name) and then
to fetch all the things by their thingids separately... so get index, and then
get each key in the index.
If a thing changes relatively
On Mar 2, 2010, at 4:17 PM, ext Jonathan Ellis wrote:
> On Tue, Mar 2, 2010 at 4:13 PM, wrote:
>> I'm exploring data layouts and it seems like the common practice is to store
>> an index in one CF (e.g. userid for row key and thingid for column name) and
>> then to fetch all the things by thei
And the only thing worse than a wiki is a wiki plus a blog plus five social
networks plus a website built on Rails plus SMS notifications plus ... :)
Jeremey.
On Mar 2, 2010, at 10:43 PM, ext Jonathan Ellis wrote:
> If there's one thing that's worse than a mailing list as a job board,
> it's a
I think you want port 9160, not ... dt_socket != thrift.
Jeremey.
On Mar 4, 2010, at 2:02 AM, ext J T wrote:
> Hi,
>
> I've been trying to piece together some notion of how to use cassandra from
> an erlang client.
>
> So far I have managed to come up with the following, but it doesn't wo
