Sounds like the consensus is that if this is a good idea at all, it needs to be opt-in. Like I said earlier, I can live with that.
On Wed, Nov 16, 2011 at 10:35 AM, Jake Luciani <jak...@gmail.com> wrote: > Having worked at places where you get fired if software *attempts* to > contact outside world I understand the concerns. > > However, if it's opt-in via config file and requires a restart then there > is no reason why it should be a concern. > > > On Wed, Nov 16, 2011 at 3:29 AM, Zhu Han <schumi....@gmail.com> wrote: > >> On Wed, Nov 16, 2011 at 3:03 PM, Norman Maurer <nor...@apache.org> wrote: >> >> > 2011/11/16 Jonathan Ellis <jbel...@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 >> > >> > > > > -- > http://twitter.com/tjake > -- Jonathan Ellis Project Chair, Apache Cassandra co-founder of DataStax, the source for professional Cassandra support http://www.datastax.com
