Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 57480 invoked from network); 17 Feb 2010 15:51:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 17 Feb 2010 15:51:23 -0000 Received: (qmail 19923 invoked by uid 500); 17 Feb 2010 15:51:22 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 19900 invoked by uid 500); 17 Feb 2010 15:51:22 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 19891 invoked by uid 99); 17 Feb 2010 15:51:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 15:51:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Feb 2010 15:51:14 +0000 Received: by fg-out-1718.google.com with SMTP id 22so13204fge.0 for ; Wed, 17 Feb 2010 07:50:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type; bh=GJ82z64RhCBuFL0IcoVS1YjRQJHgs0Fd1dJ/feiqcYg=; b=tFiQbQhwj7F4A+61ygSIXxoMvTQzJ9yGIvhg0OMlhhy5Yb355wdgnrQX6VrqMhaeZK bB2CmySZ3TVwE1g8ZULKXoReQbr43I/Xdf3UttVzqX/A1ff2uMM9mwAR3pOEsm5jgkjL om33e/pQr2B3bV4ZCCH+jmkRv+9LlRCFBUY/g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=hMlsQnYXrioij0N7ckd411cZ2yRkyaBfCYOpDnlCqRDHDzyHEkB2+dvBfQviekvgl8 ImLoyVY8tGT2BRkxa7T0+3Mzl9t9/1Wu83bgR7UaoHpVKU3HR2mVXjk0qHPQwXYsI+Ui 7bz/6cEx5OsZF49edAAKCcXWUUVP78nzGxIdo= MIME-Version: 1.0 Received: by 10.216.157.130 with SMTP id o2mr3201121wek.160.1266421854336; Wed, 17 Feb 2010 07:50:54 -0800 (PST) In-Reply-To: <9b048d181002170748t7379dcfen57537618ec97459b@mail.gmail.com> References: <9b048d181002170748t7379dcfen57537618ec97459b@mail.gmail.com> From: Jonathan Ellis Date: Wed, 17 Feb 2010 09:50:34 -0600 Message-ID: Subject: Re: Row with many columns To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org you are correct, partitioning is entirely by row key. as long as your number of rows is an order of magnitude or two more than your node count in your cluster though, that doesn't really matter. On Wed, Feb 17, 2010 at 9:48 AM, ruslan usifov wrote: > Hello > > For example if we have table, which have rows with many columns (10000 or > more) how this data will by partitioned?? I expect that one row may by slit > on some nodes. But look at source of cassandra i think that one row store on > one node, and never slits, or i be mistaken??