Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of 0x6e6562@gmail.com designates
 209.85.216.51 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CC9061EC.2E62D%boneill42@gmail.com>
References: 
 <CAB-G1jgJJ7_z++Qz8fQ4ojkdz8sBu8nEWGe1MDPVUquA4OziJQ@mail.gmail.com>
	<CC9061EC.2E62D%boneill42@gmail.com>
Date: Tue, 2 Oct 2012 14:55:05 +0100
Message-ID: 
 <CAB-G1jg08T1DPhuunubrNk1o_EKWyauFcFefkMO9HCqqQh1fCw@mail.gmail.com>
Subject: Re: 1000's of column families
From: Ben Hood <0x6e6562@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Brian,

On Tue, Oct 2, 2012 at 2:20 PM, Brian O'Neill <boneill42@gmail.com> wrote:
>
> Without putting too much thought into it...
>
> Given the underlying architecture, I think you could/would have to write
> your own partitioner, which would partition based on the prefix/virtual
> keyspace.

I might be barking up the wrong tree here, but looking at source of
ColumnFamilyInputFormat, it seems that you can specify a KeyRange for
the input, but only when you use an order preserving partitioner. So I
presume that if you are using the RandomPartitioner, you are
effectively doing a full CF scan (i.e. including all tenants in your
system).

Ben