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 180D27D21 for ; Mon, 1 Aug 2011 22:08:48 +0000 (UTC) Received: (qmail 94128 invoked by uid 500); 1 Aug 2011 22:08:45 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 94020 invoked by uid 500); 1 Aug 2011 22:08:45 -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 94012 invoked by uid 99); 1 Aug 2011 22:08:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2011 22:08:44 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,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 teddyyyy123@gmail.com designates 209.85.161.172 as permitted sender) Received: from [209.85.161.172] (HELO mail-gx0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2011 22:08:37 +0000 Received: by gxk19 with SMTP id 19so4460194gxk.31 for ; Mon, 01 Aug 2011 15:08:16 -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=6EQjlH4op2OCCZA+yWnYaFSZ5TQje800afeiHCmu+X4=; b=HPYbp6qF20i7lxX12Cy+i5i+FX3VBEthTOAGZUZTIzHNNNQ8nO0RjbDDUkPTs0p9TY UYAtFuNbMqYbGnh2anWKeVlNtxmfHI5W36rt4QsL3X4qAldpPLFSiA0EDgdMwxFK6429 uFYQpShQtBA7bS4pFZpl170EN1KdJZk+xI9UQ= MIME-Version: 1.0 Received: by 10.236.115.231 with SMTP id e67mr3832478yhh.222.1312236496312; Mon, 01 Aug 2011 15:08:16 -0700 (PDT) Received: by 10.236.60.134 with HTTP; Mon, 1 Aug 2011 15:08:16 -0700 (PDT) Date: Mon, 1 Aug 2011 15:08:16 -0700 Message-ID: Subject: implications of using more keyspaces vs single keyspace? From: Yang To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org for example my data consists of "salary", "office stationery list", let's say I do use the same replicationStrategy for them, these 2 data sets have different key ranges, key distributions, then is it better to use separate keyspaces for each of them? or use a single one? the factors I can think of: separate: have to call set_keyspace() if your calls switch between datasets potential to change to different replication factor in the future any thoughts? Thanks a lot Yang