From user-return-21822-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org  Thu Oct 27 05:29:06 2011
Return-Path: <user-return-21822-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org>
X-Original-To: apmail-cassandra-user-archive@www.apache.org
Delivered-To: apmail-cassandra-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 9153A94F1
	for <apmail-cassandra-user-archive@www.apache.org>; Thu, 27 Oct 2011 05:29:06 +0000 (UTC)
Received: (qmail 7584 invoked by uid 500); 27 Oct 2011 05:29:04 -0000
Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org
Received: (qmail 7565 invoked by uid 500); 27 Oct 2011 05:29:04 -0000
Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@cassandra.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@cassandra.apache.org>
List-Post: <mailto:user@cassandra.apache.org>
List-Id: <user.cassandra.apache.org>
Reply-To: user@cassandra.apache.org
Delivered-To: mailing list user@cassandra.apache.org
Received: (qmail 7557 invoked by uid 99); 27 Oct 2011 05:29:03 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 05:29:03 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of yulinyen@gmail.com designates 209.85.215.172 as permitted sender)
Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 27 Oct 2011 05:28:55 +0000
Received: by eyg24 with SMTP id 24so2246713eyg.31
        for <user@cassandra.apache.org>; Wed, 26 Oct 2011 22:28:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=qzGp/zXMzWfokZoVNYDsbfiSigcqXoIy+pE5twSUFsA=;
        b=Y5/kYjgUOFehn1x8CT7FU6L+EE1bztLoV7RzlIxEpvvlBuvxqhOXeDmeDDRqba+hE3
         P6c1TGO7tKbadJffYnWCoQTDahIUNWNiMhELT8+45Yu/iib/pJpE8wXoWxCK8mXNh26z
         K1s6Nx8cajDxKA9++H1KKGBnr9OClom779ZEc=
MIME-Version: 1.0
Received: by 10.14.18.26 with SMTP id k26mr4254759eek.5.1319693315511; Wed, 26
 Oct 2011 22:28:35 -0700 (PDT)
Received: by 10.14.47.80 with HTTP; Wed, 26 Oct 2011 22:28:35 -0700 (PDT)
Date: Thu, 27 Oct 2011 13:28:35 +0800
Message-ID: <CAAaMp526D127xCtiej3gXPijtWx0okK9wsP79MBSunWdz_H-RQ@mail.gmail.com>
Subject: multiple keyspace vs single keyspace
From: Boris Yen <yulinyen@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016e659fe1a48952504b0410bdb
X-Virus-Checked: Checked by ClamAV on apache.org

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

Hi,

We plan to put data into different keyspaces, e.g a keyspace specific to
save our own configurations, a keyspace to save data like events, devices
and some other keyspaces to save other type of data. Is there any limitation
on this kind of design. Any pros or cons?

Regards
Boris

--0016e659fe1a48952504b0410bdb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>We plan to put data into different keyspaces, e.g a =
keyspace specific to save our own configurations, a keyspace to save data l=
ike events, devices and some other keyspaces to save other type of data. Is=
 there any limitation on this kind of design. Any pros or cons?</div>
<div><br></div><div>Regards</div><div>Boris</div><div><br></div><div><br></=
div>

--0016e659fe1a48952504b0410bdb--