What about if I spread these columns across 20 rows ? Then I have to
query each of these 20 rows for 500 columns. but still this seems a
better solution than one row for all cols or separate row for each
email id approaches !?
On Fri, Jul 27, 2012 at 11:36 AM, Aklin_81 wrote:
> Sorry for the conf
Sorry for the confusion created. I need to store emails registered
just for a single application. So although my data model would fit
into just a single row. But is storing a hundred million columns(col
name size= 8 byte; col value size=4 byte ) in a single row a good idea
? I am very much tempted
In general I believe wide rows (many cols ) are preferable to skinny rows
(many rows) so that you can get all the information in 1 go,
One can store 2 billion cols in a row.
However, on what basis would you store the 500 email ids in 1 row? What
can be the row key?
For e.g. If the query you want t
Yeah, I was talking about create a ColumnFamily definition via the API. Not inserting data into an already defined column family. The recommened approach to creating your schema is via the build in bin/cassandra-cli command line tool. It has loads of build in help and here is an example of how to c
I'm fairly certain Aaron is referring to named families like BlogEntries,
not named columns (i-got-a-new-guitar).
On Tue, Jan 25, 2011 at 4:37 AM, Andy Burgess
wrote:
> Aaron,
>
> A question about one of your general points, "do not create CF's on the
> fly" - what, exactly, does this mean? Do y
Aaron,
A question about one of your general points, "do not create CF's on
the fly" - what, exactly, does this mean? Do you mean named column
families, like "BlogEntries" from Sam's example, or do you mean
column family keys, like "i-got-a-new-guitar"? If it's the l
Sam, The best advice is to jump in and try any schema If you are just starting out, start simple you're going to re-write it several times. Worry about scale later, in most cases it's going to work. Some general points:- do not create CF's on the fly. - work out your common read requests and denorm
On Sun, Oct 3, 2010 at 11:02 AM, Simon Reavely wrote:
> Two questions:
> 1. So this compaction challenge is a CPU issue or a disk IO issue in your
> case?
> 2. In other places people have recommended adjustments from the defaults to
> control compaction overhead...did you adjust or experiment wi
Two questions:
1. So this compaction challenge is a CPU issue or a disk IO issue in your case?
2. In other places people have recommended adjustments from the defaults to
control compaction overhead...did you adjust or experiment with how to control
compaction?
Simon Reavely
On Sep 21, 201
On Tue, Sep 21, 2010 at 5:01 PM, Morten Wegelbye Nissen wrote:
> There is a point here that is very important. The key, is erhhm the key to
> success. Ie. you must build the key in a way where you can find it again.
Yes. You must index your data (choose your key and column names) in
such that it
Thanks,
There is a point here that is very important. The key, is erhhm the key
to success. Ie. you must build the key in a way where you can find it again.
In case you create a system for login, you would most likely have the
login name as key. ( And maybe here link that to a userid that wi
Not really. The schema has worked without any problems and we haven't
had any problems with it. We're running a five node cassandra cluster
behind the system (it has also other uses than just this particular
application like it stores all our blog contents and bunch of other
data). There are about
Thanks for the writeup...good stuff!
Any lessons learnt you'd like to share or challenges that persist?
Simon Reavely
On Sep 20, 2010, at 6:37 AM, Juho Mäkinen wrote:
> We have built a facebook style "messenger" into our web site which
> uses cassandra as storage backend with two column famil
We have built a facebook style "messenger" into our web site which
uses cassandra as storage backend with two column families:
TalkMessages and TalkLastMessages. I've uploaded a screenshot showing
the feature in action to
http://img138.imageshack.us/img138/3807/talkexample.jpg
TalkMessages contain
Hi Morten
Simplest appraoch that comes to my mind (without considering any other use
-cases just read and unread messages) is to use two CF's 'read' and
'unread', put all new messages in 'unread' and once user reads any one one
them shift the same to 'read' and mark original for deletion.
Regard
Here is a discussion about implementing twitter with Cassandra
http://www.rackspacecloud.com/blog/2010/05/12/cassandra-by-example/
An example of the same on github
http://github.com/ericflo/twissandra
If you have not done already checkout the articles page on the wiki
http://wiki.apache.org/cas
Hello List,
No matter where you read, you almost every-where read the the noSQL
datascema is completely different from the relational way - and after a
little insight in cassandra everyone can 2nd that.
But I miss to see some real-life examples on how a real system can be
modelled. Lets tak
17 matches
Mail list logo
