Return-Path: 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 9493DCC3A for ; Thu, 13 Nov 2014 16:42:42 +0000 (UTC) Received: (qmail 15184 invoked by uid 500); 13 Nov 2014 16:42:39 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 15145 invoked by uid 500); 13 Nov 2014 16:42:39 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 15135 invoked by uid 99); 13 Nov 2014 16:42:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2014 16:42:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of guangxing.li@pearson.com designates 67.231.144.81 as permitted sender) Received: from [67.231.144.81] (HELO mx0a-000e6001.pphosted.com) (67.231.144.81) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 13 Nov 2014 16:42:33 +0000 Received: from pps.filterd (m0000475.ppops.net [127.0.0.1]) by m0000475.ppops.net (8.14.5/8.14.5) with SMTP id sADGcrPY004469 for ; Thu, 13 Nov 2014 11:42:10 -0500 Received: from mail-qa0-f43.google.com (mail-qa0-f43.google.com [209.85.216.43]) by m0000475.ppops.net with ESMTP id 1qmrkv0psb-1 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT) for ; Thu, 13 Nov 2014 11:42:09 -0500 Received: by mail-qa0-f43.google.com with SMTP id j7so10527100qaq.30 for ; Thu, 13 Nov 2014 08:42:07 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=zh/UbFrGh4EcrzQbyI2qfmLq58yjHzFPE1j2GKJjTGY=; b=XfQ5U952lQ37OL8cRmzHANIQ83r99vvjRr4KYUoTBYRyJSWzPFF+23r5HiNsiZAGOR NWAwmXqxyOg0KD4WtVBIMfUXNE6RQwMifJTIIQuKh7EjKkLKsin75c45argYH0cXVpVo 6/H/sY9IQx5fU4EsI1y4rXqX4K9+XyA9tQENY0Yq4OU2n/Mek42HitgeXN6TQNNjbOW4 yT9jFhcRcTHtrc0uAXYkHn+jhhu7DELoycKYtYnz/h7zZILd1msF0GUamOIo4Zfd7sH7 cB0MMskPVPtpbP+UK70TGpBB9niJiFk+8CViSP09tg3OObsnlRUpUtZE+897uvOzg2mM nR1w== X-Gm-Message-State: ALoCoQmxi4mYPKxECg+mjICTNn22lE+RhP5kdaPOKQt2VvKodytT0exkJwkKuwizy0Rnpv5G14Wzg/aBWSY5ZCiY+qENHre7Fg007vIU5tBs0L9O20TNsC2C0zSTJKFnpVaMKfTNcOH1D70T8JjYy4RFE53O3lGB+Q4rA1PpBrpF7DRIfJkSJ/g= X-Received: by 10.224.92.81 with SMTP id q17mr4358092qam.66.1415896927047; Thu, 13 Nov 2014 08:42:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.224.92.81 with SMTP id q17mr4358077qam.66.1415896926935; Thu, 13 Nov 2014 08:42:06 -0800 (PST) Received: by 10.229.156.200 with HTTP; Thu, 13 Nov 2014 08:42:06 -0800 (PST) Date: Thu, 13 Nov 2014 09:42:06 -0700 Message-ID: Subject: Is it more performant to split data with the same schema into multiple keyspaces, as supposed to put all of them into the same keyspace? From: "Li, George" To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e0153867c5e7bb70507c03165 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.28,0.0.0000 definitions=2014-11-13_07:2014-11-13,2014-11-13,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1411130129 X-Virus-Checked: Checked by ClamAV on apache.org --089e0153867c5e7bb70507c03165 Content-Type: text/plain; charset=UTF-8 Hi, we use Cassandra to store some association type of data. For example, store user to course (course registrations) association and user to school (school enrollment) association data. The schema for these two types of associations are the same. So there are two options to store the data: 1. Put user to course association data into one keyspace, and user to school association data into another keyspace. 2. Put both of them into the same keyspace. In the long run, such data will grow to be very large. With that in mind, is it better to use the first approach (having multiple keyspaces) for better performance? Thanks. George --089e0153867c5e7bb70507c03165 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,
we use Cassandra to store some associat= ion type of data. For example, store user to course (course registrations) = association and user to school (school enrollment) association data. The sc= hema for these two types of associations are the same. So there are two opt= ions to store the data:
1. Put user to course=C2=A0association=C2= =A0data into one keyspace, and user to school=C2=A0association=C2=A0data in= to another keyspace.
2. Put both of them into the same keyspace.<= /div>
In the long run, such data will grow to be very large. With that = in mind, is it better to use the first approach (having multiple keyspaces)= for better performance?
Thanks.

George<= /div>
--089e0153867c5e7bb70507c03165--