From user-return-17358-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Sun Jun 5 18:17:35 2011 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 D15F46E69 for ; Sun, 5 Jun 2011 18:17:35 +0000 (UTC) Received: (qmail 99396 invoked by uid 500); 5 Jun 2011 18:17:32 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 99369 invoked by uid 500); 5 Jun 2011 18:17:32 -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 99361 invoked by uid 500); 5 Jun 2011 18:17:32 -0000 Delivered-To: apmail-incubator-cassandra-user@incubator.apache.org Received: (qmail 99358 invoked by uid 99); 5 Jun 2011 18:17:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Jun 2011 18:17:32 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=FREEMAIL_FROM,RFC_ABUSE_POST,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted nor denied by domain of mohitanchlia@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 Jun 2011 18:17:27 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QTHso-0003ZL-KQ for cassandra-user@incubator.apache.org; Sun, 05 Jun 2011 11:17:06 -0700 Date: Sun, 5 Jun 2011 11:17:06 -0700 (PDT) From: mcasandra To: cassandra-user@incubator.apache.org Message-ID: <1307297826627-6442802.post@n2.nabble.com> In-Reply-To: References: Subject: Re: Direct control over where data is stored? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Please give more detailed info about what exactly you are worried about or trying to solve. Please take a step back and look at cassandra's architecture again and what it's trying to solve. It's a distributed database so if you do what you are describing there is a potential of getting hotspots. Which will probably lead in other problems. You might solve one problem but then intriduce another like slow reads or one node getting overloaded. IF you really want to do what you described you can solve it simply by designing your data model in that way. For eg: For User A you can store information for all it's friends. This will lead to duplicate data but will solve your problem. I also suggest run some stress test and worry about the load, performance only if it is a real problem for your kind of data. -- View this message in context: http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Direct-control-over-where-data-is-stored-tp6441048p6442802.html Sent from the cassandra-user@incubator.apache.org mailing list archive at Nabble.com.