Re: CQL and undefined columns

; and > you "should probably avoid it" is wrong. > > In many cases compact storage it is the best way to store things, because > it is the smallest. > > > > > On Mon, Aug 5, 2013 at 4:57 PM, Jonathan Haddad wrote: > >> If you expected your CQL3 query to

Re: Issue with CQLsh

My understanding is that if you want to use CQL, you should create your tables via CQL. Mixing thrift calls w/ CQL seems like it's just asking for problems like this. On Sun, Aug 25, 2013 at 6:53 PM, Vivek Mishra wrote: > cassandra 1.2.4 > > > On Mon, Aug 26, 2013 at 2:51 AM, Nate McCall wrote

Re: Cluster Management

An alternative to cssh is fabric. It's very flexible in that you can automate almost any repetitive task that you'd send to machines in a cluster, and it's written in python, meaning if you're in AWS you can mix it with boto to automate pretty much anything you want. On Thu, Aug 29, 2013 at 4:25

Re: Low Row Cache Request

9/12 = .75 It's a rate, not a percentage. On Sat, Aug 31, 2013 at 2:21 PM, Sávio Teles wrote: > I'm running one Cassandra node -version 1.2.6- and I *enabled* the *row > cache* with *1GB*. > But looking the Cassandra metrics on JConsole, *Row Cache Requests* are > very *low* a

Re: is there any type of table existing on all nodes(slow to up date, fast to read in map/reduce)?

You could create a bunch of 1 node DCs if you really wanted it. On Fri, Sep 13, 2013 at 12:29 PM, Hiller, Dean wrote: > Actually, I have been on a few projects where something like that is > useful. Gemfire(a grid memory cache) had that feature which we used at > another company. On every pro

Re: Why don't you start off with a “single & small” Cassandra server as you usually do it with MySQL?

For future references, a blog post on this topic. http://rustyrazorblade.com/2013/09/cassandra-faq-can-i-start-with-a-single-node/ On Wed, Sep 18, 2013 at 6:38 AM, Michał Michalski wrote: > You might be interested in this: > http://mail-archives.apache.**org/mod_mbox/cassandra-user/**201308.mbo

Re: Organize model for range scans in Cassandra

I'd avoid using super columns. I don't believe they're recommended anymore, and with CQL3 they aren't even supported (if you're interested in going that route). I think it's unlikely that you'll want a column family per company either. How many "ticker" entries do you plan on writing per company

<    1   2   3   4   5   6