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 7953A73F4 for ; Thu, 25 Aug 2011 05:22:01 +0000 (UTC) Received: (qmail 83611 invoked by uid 500); 25 Aug 2011 05:21:55 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83264 invoked by uid 500); 25 Aug 2011 05:21:30 -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 82950 invoked by uid 99); 25 Aug 2011 05:21:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2011 05:21:22 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of prvs=211bf81fb=himanshi.sharma@tcs.com designates 121.242.48.3 as permitted sender) Received: from [121.242.48.3] (HELO inblrg01.tcs.com) (121.242.48.3) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2011 05:21:14 +0000 X-IronPort-AV: E=Sophos;i="4.68,279,1312137000"; d="scan'208";a="52624734" In-Reply-To: References: To: user@cassandra.apache.org MIME-Version: 1.0 Subject: Re: For multi-tenant, is it good to have a key space for each tenant? X-KeepSent: CD420F1B:E8305E3A-652578F7:001C5EBD; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 February 07, 2008 From: Himanshi Sharma X-MIMETrack: S/MIME Sign by Notes Client on Himanshi Sharma/TVM/TCS(Release 8.0.1|February 07, 2008) at 08/25/2011 10:50:16 AM, Serialize by Notes Client on Himanshi Sharma/TVM/TCS(Release 8.0.1|February 07, 2008) at 08/25/2011 10:50:16 AM, Serialize complete at 08/25/2011 10:50:16 AM, S/MIME Sign failed at 08/25/2011 10:50:16 AM: The cryptographic key was not found, Serialize by Router on InBlrM10/TCS(Release 8.5.2FP2|March 22, 2011) at 08/25/2011 10:50:50, Serialize complete at 08/25/2011 10:50:50 Message-ID: Date: Thu, 25 Aug 2011 10:50:48 +0530 Content-Type: multipart/alternative; boundary="=_alternative 001D527E652578F7_=" X-Virus-Checked: Checked by ClamAV on apache.org This is a multipart message in MIME format. --=_alternative 001D527E652578F7_= Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" I am working on similar sort of stuff. As per my knowledge, creating keyspace for each tenant would impose lot of memory constraints. Following Shared Keyspace and Shared Column families would be a better approach. And each row in CF could be referred by tenant_id as row key. And again it depends on the type of application. Hey this is just a suggestion, m not completely sure.. :) Himanshi Sharma From: Guofeng Zhang To: user@cassandra.apache.org Date: 08/25/2011 10:38 AM Subject: For multi-tenant, is it good to have a key space for each tenant? I wonder if it is a good practice to create a key space for each tenant. Any advice is appreciated. Thanks =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you --=_alternative 001D527E652578F7_= Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="us-ascii"
I am working on similar sort of stuff. As per my knowledge, creating keyspace for each tenant would impose lot of memory constraints.

Following Shared Keyspace and Shared Column families would be a better approach. And each row in CF could be referred by tenant_id as row key.
And again it depends on the type of application.

Hey this is just a suggestion, m not completely sure.. :)


Himanshi Sharma




From: Guofeng Zhang <guofengzh@gmail.com>
To: user@cassandra.apache.org
Date: 08/25/2011 10:38 AM
Subject: For multi-tenant, is it good to have a key space for each tenant?




I wonder if it is a good practice to create a key space for each tenant. Any advice is appreciated.

Thanks 


=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


--=_alternative 001D527E652578F7_=--