r or Standard CF will make little performance
difference, other the super CF limitations mentioned.
Aaron
On 18/01/2011, at 11:14 PM, Steven Mac wrote:
Thanks for the answer. It provides me the insight I'm looking for.
However, I'm also a bit confused as your first paragraph seems to indica
the limitations page on the wiki.
Hope that helps.Aaron
On 18/01/2011, at 9:29 PM, Steven Mac wrote:
Some of the fields are indeed written in one shot, but others (such as label
and categories) are added later, so I think the question still stands.
Hugo.
From: dri...@gmail.com
Date: Mon,
, 2011 at 5:12 PM, Steven Mac wrote:
I guess I was maybe trying to simplify the question too much. In reality I do
not have one volatile part, but multiple ones (say all trading data of day).
Each would be a supercolumn identified by the time slot, with the individual
fields as subcolumns
com
> To: user@cassandra.apache.org
>
> On 17 January 2011 22:36, Steven Mac wrote:
> > Sure, consider stock data, where the stock symbol is the row key. The stock
> > data consists of a rather stable part and a very volatile part, both of
> > which would be a super column. The stable
Subject: Re: Super CF or two CFs?
From: davevi...@gmail.com
To: user@cassandra.apache.org
can you give an example of the data and how you'd access it?what would your
expected columns (and/or supercolumns) be?
Dave Viner
On Mon, Jan 17, 2011 at 11:05 AM, Steven Mac wrote:
How can I bes
How can I best map an object containing two maps, one of which is updated very
frequently and the other only occasionally?
a) As one super CF, which each map in a separate supercolumn and the map
entries being the subcolumns?
b) As two CFs, one for each map.
I'd like to discuss the why behind
> Date: Thu, 13 Jan 2011 01:29:33 +0100
> Subject: Re: Advice wanted on modeling
> From: peter.schul...@infidyne.com
> To: user@cassandra.apache.org
>
> > The application will have a large number of records, with the records
> > consisting of a fixed part and a number (n) of periodic parts.
> > *
Hi,
I've been experimenting quite a bit with Cassandra and think I'm getting to
understand it, but I would like some advice on modeling my data in Cassandra
for an application I'm developing.
The application will have a large number of records, with the records
consisting of a fixed part and
