Return-Path: X-Original-To: apmail-cassandra-dev-archive@www.apache.org Delivered-To: apmail-cassandra-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D211A7BA7 for ; Fri, 18 Nov 2011 00:02:32 +0000 (UTC) Received: (qmail 17390 invoked by uid 500); 18 Nov 2011 00:02:31 -0000 Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org Received: (qmail 17367 invoked by uid 500); 18 Nov 2011 00:02:31 -0000 Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list dev@cassandra.apache.org Received: (qmail 17359 invoked by uid 99); 18 Nov 2011 00:02:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2011 00:02:31 +0000 X-ASF-Spam-Status: No, hits=0.7 required=5.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [219.76.94.32] (HELO ocmas07.netvigator.com) (219.76.94.32) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Nov 2011 00:02:23 +0000 Received: from wsgmta01.netvigator.com ([219.76.94.14]) by ocmas07.netvigator.com with bizsmtp id yN061h0010Jc1Qj01Q1zyy; Fri, 18 Nov 2011 08:01:59 +0800 Received: from [10.42.202.134] ([123.136.7.134]) by wsgmta01.netvigator.com with bizsmtp id yQ1w1h00B2tWNPv01Q1yCb; Fri, 18 Nov 2011 08:01:59 +0800 Subject: Re: How is Cassandra being used? References: <4EC43FF9.2040405@dehora.net> <4EC56026.5070607@sendmail.cz> From: Dop Sun Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (9A405) In-Reply-To: <4EC56026.5070607@sendmail.cz> Message-Id: <21F0D137-2C13-47C5-96F7-9576E9C86554@dopsun.com> Date: Fri, 18 Nov 2011 08:01:53 +0800 To: "dev@cassandra.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) I am not dev of cassandra, sub this list because i'm dev for app using it. To me, this (phone home) opens a door, and it may designed to be used only f= or carefully selected anonymous data: 1) but software has at least one bug (side effect), what happen it sends som= ething more accidentally? Also, even today data we believe safe, but tomorro= w it may turn out to be classified as sensitive, and you can not take back d= ata which already out of door. 2) risk for future versions, this forces all upgrades to include review of t= his anonymous data (if door opened, it is too easy to add a little bit next t= ime, and next...), imagin every release, to invite compliance team to sign o= ff... it may slow the adoption of new versions. And this does no good for he= athy of Cassandra community/ user group. As a user may not be right to vote here, but if I vote: -1 for introducing this feature at all But if it's eventually included: +1 for separate code/ jar =20 On 18 Nov, 2011, at 3:27 AM, Radim Kolar wrote: > Dne 16.11.2011 23:58, Bill napsal(a): >> We'll turn this off, and would possibly patch it out of the code. That's n= ot to say it wouldn't be useful to others. > we patch out of code spyware in ehcache and quartz too. This is only way t= o be sure that it will not be enabled by configuration mistake. >=20 > We had similar stuff in our software (just version check) and had to remov= e it after 14 days of customer complains. As correctly stated in comments - y= ou will get results from self selecting group and this group will not includ= e most important deployments running cassandra in production. >=20 > There is zero benefit for company allowing cassandra to spy how many nodes= , data, rows and CF they have and its bad idea to implement spyware into app= lication used for working with sensitive data.