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 9A3DBFAB5 for ; Fri, 12 Dec 2014 17:22:13 +0000 (UTC) Received: (qmail 61266 invoked by uid 500); 12 Dec 2014 17:22:10 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 61221 invoked by uid 500); 12 Dec 2014 17:22:10 -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 61211 invoked by uid 99); 12 Dec 2014 17:22:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 17:22:10 +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 (nike.apache.org: domain of mightye@gmail.com designates 209.85.214.179 as permitted sender) Received: from [209.85.214.179] (HELO mail-ob0-f179.google.com) (209.85.214.179) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 17:21:44 +0000 Received: by mail-ob0-f179.google.com with SMTP id va2so9273786obc.10 for ; Fri, 12 Dec 2014 09:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=U0DEF+01rrF+dKwcrLSsHnjJ0JT8OpL7BJOoAj8Fp5c=; b=FjhcEqy3EaqOckeLeNxnVBoPMXD0HfxEZO57+uKlNoFUTtx+80H4OWmmpwxqntyr8t t5aNsJfaC1lkeouyPRMkiWG6+YRmbJhD7OhCeWTejZA6W5eK8mqA2HY1cQ+ei6+Yr144 xZQjFj+0/9oHm+9LhLX7dOmQZy1dva72lsvQWVpznd4QZiNL7xoRpE2Dz/PLnTXG3Pth iZc2YdXfJNrzEh+0MEsqtE9L9bkCjfjMDI7RTATb3mSgbgcwSbKxSjwPIvpQkGRejlF4 J08ZBjA/V38XrhI8p0wRde79zeb91fXqjPvzq8thwG51zupQIikdBJqy5K7eUmO3SRdz dZpg== X-Received: by 10.182.33.138 with SMTP id r10mr10794495obi.67.1418404903147; Fri, 12 Dec 2014 09:21:43 -0800 (PST) MIME-Version: 1.0 From: Eric Stevens Date: Fri, 12 Dec 2014 17:21:42 +0000 Message-ID: Subject: Using Per-Table Keyspaces for Tunable Replication To: "user@cassandra.apache.org" Content-Type: multipart/alternative; boundary=001a11c2cb9a666197050a08201b X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2cb9a666197050a08201b Content-Type: text/plain; charset=UTF-8 We're considering moving to a model where we put each of our tables in a dedicated keyspace. This is so we can tune replication per table, and change our mind about that replication on a per-table basis without a major migration. The biggest driver for this is Solr integration, we want to tune RF into our Solr DC such that only tables which we want to search are sent there (using NetworkTopologyStrategy with 'solr': 0 for tables which are not searchable). Has anyone else tried this, is there any reason we might not want to do so? Any hidden gotchas we should be concerned about? Our total table count is small, in the tens range; our searchable tables are maybe 4 or 5. --001a11c2cb9a666197050a08201b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable We're considering moving to a model where we put each of our tables in = a dedicated keyspace.=C2=A0 This is so we can tune replication per table, a= nd change our mind about that replication on a per-table basis without a ma= jor migration.=C2=A0 The biggest driver for this is Solr integration, we wa= nt to tune RF into our Solr DC such that only tables which we want to searc= h are sent there (using NetworkTopologyStrategy with 'solr': 0 for = tables which are not searchable).

Has anyone else tried = this, is there any reason we might not want to do so?=C2=A0 Any hidden gotc= has we should be concerned about?=C2=A0 Our total table count is small, in = the tens range; our searchable tables are maybe 4 or 5.
--001a11c2cb9a666197050a08201b--