Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of schumi.han@gmail.com designates
 209.85.213.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAKrGPjyr4vM2iGK5fx+jv05B94zqBbvpptw_VJr2wRL5QzWfAg@mail.gmail.com>
References: 
 <CALdd-zi-MqBzjA4fqBc8y5XANya8F1_rBCR=s49PEGg+Kx6BjA@mail.gmail.com>
	<CAKrGPjyr4vM2iGK5fx+jv05B94zqBbvpptw_VJr2wRL5QzWfAg@mail.gmail.com>
Date: Wed, 16 Nov 2011 16:29:58 +0800
Message-ID: 
 <CAF7KpS8dk0sSZn-AtRML=0MjtxBN83b=_7NrXydOR4O0cxJzug@mail.gmail.com>
Subject: Re: How is Cassandra being used?
From: Zhu Han <schumi.han@gmail.com>
To: dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016e68e9a2ccf7d5704b1d5e82d

--0016e68e9a2ccf7d5704b1d5e82d
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 16, 2011 at 3:03 PM, Norman Maurer <norman@apache.org> wrote:

> 2011/11/16 Jonathan Ellis <jbellis@gmail.com>:
> > 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:
> > 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.
> >
> > (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 apache.org 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?
>

-1.

It may scare some admins who stores sensitive data  in cassandra. Even if
it can
disabled, we can not sleep well in the night when we know the door can be
opened unintentionally...


> Hi there,
>
> I'm not a cassandra dev but an user of it. I would really "hate" to
> see such code in the cassandra code-base. I understand that it would
> be kind of useful to get a better feeling about usage etc, but its
> really something that scares the shit out of many managers (and even
> devs ;) ).
>
> So -1 to add this code (*non-binding)
>
> Bye,
> Norman
>

--0016e68e9a2ccf7d5704b1d5e82d--