incubator-cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gary Dusbabek <>
Subject Re: How is Cassandra being used?
Date Wed, 16 Nov 2011 14:46:27 GMT
On Tue, Nov 15, 2011 at 17:23, Jonathan Ellis <> wrote:
> I started a "users survey" thread over on the users list (replies are
> still trickling in), but as useful as that is, I'd like to get
> feedback that is more quantitative and with a broader base.  This will
> let us prioritize our development efforts to better address what
> people are actually using it for, with less guesswork.  For instance:

If we're having a hard time prioritizing work on Cassandra we should
consider if the work left is not worth doing or is all the same

> we put a lot of effort into compression for 1.0.0; if it turned out
> that only 1% of 1.0.x users actually enable compression, then it means
> that we should spend less effort fine-tuning that moving forward, and
> use the energy elsewhere.

Here is what should determine where energy is spent:  if enough people
are willing to expend the effort to voice their concerns about feature
X in JIRA and on the mailing list, and there are people willing to do
the technical work, and it doesn't represent a technical Wrong Turn
for the project, then it should (it will) get worked on.

> (Of course it could also mean that we did a terrible job getting the
> word out about new features and explaining how to use them, but either
> way, it would be good to know!)
> I propose adding a basic cluster reporting feature to cassandra.yaml,
> enabled by default.  It would send anonymous information about your
> cluster to an VM.  Information like, number (but not names)
> of keyspaces and columnfamilies, ks-level options like compression, cf
> options like compaction strategy, data types (again, not names) of
> columns, average row size (or better: the histogram data), and average
> sstables per read.
> Thoughts?

IMO this well-intentioned proposal, and most of the comments have
missed the mark entirely.

As open-source software, the community should decide which features
(including this proposal) make it into Cassandra.  Isn't this how it
is supposed to work?


> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder of DataStax, the source for professional Cassandra support

View raw message