Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 74.125.78.147 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:content-transfer-encoding;
        b=Zv8MvFXrAgwgdYBBQr5MXwHl7UsUkfV1JOBMKRPOYIvN1GzSlC1ckhA9KLlfJHkuL8
         iEU57aZHQsoYBDZyT8HcBOYHy/EGCKxWBEeY3XBXN7mRuZo5mIMF6ko5kEM4V5O4pbLi
         Ie77Om+1DZ3p2xfXl7V3gFmlZJDfahXnGbmGI=
MIME-Version: 1.0
In-Reply-To: <87fx7ul6id.fsf@lifelogs.com>
References: <87eio6p7pb.fsf@lifelogs.com>
 <5B7ECCB8-BF96-4EA1-AAB7-B8C27B824FDF@quagility.com>
	<e06563880911120838r6035eac0rd380e62438945744@mail.gmail.com>
	<DC6830C8-E88C-4D2F-B4E2-A63088599D01@quagility.com>
 <e06563880911120849p4deea68dj4cc95bc9531c62d0@mail.gmail.com>
	<87fx8jptkn.fsf@lifelogs.com> <874oozpqcw.fsf@lifelogs.com>
	<87einfr6a8.fsf@lifelogs.com> <1259699027.19220.37.camel@achilles>
	<87fx7ul6id.fsf@lifelogs.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Tue, 1 Dec 2009 17:13:24 -0600
Message-ID: <e06563880912011513x357b0e8bmea9b9d03a8dcf03f@mail.gmail.com>
Subject: Re: Cassandra access control
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

2009/12/1 Ted Zlatanov <tzz@lifelogs.com>:
> I disagree, why would you want to forbid switching the keyspace? =A0That'=
s
> turning off a currently working feature. =A0Also, connections are not
> free, especially across WAN links.

It's a currently working feature that (a) only exists in the first
place because it was less bad than postponing 0.4 until we could add
something like this auth feature, and (b) is of entirely theoretical
benefit in the sense that nobody who wants to keep it actually has an
app using it, to the best of my knowledge.

Let's correct our error, and only add functionality that we know is
really needed -- and even then, only if the benefit outweighs the
complexity price -- rather than waving our hands and saying "maybe
someone will need it, someday."  That way leads to clutter and bloat.

-Jonathan