From user-return-27066-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Mon Jun 18 17:19:30 2012 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 D76AF96F4 for ; Mon, 18 Jun 2012 17:19:30 +0000 (UTC) Received: (qmail 14716 invoked by uid 500); 18 Jun 2012 17:19:28 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 14644 invoked by uid 500); 18 Jun 2012 17:19:28 -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 14592 invoked by uid 99); 18 Jun 2012 17:19:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 17:19:26 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of cyril.auburtin@gmail.com designates 209.85.161.172 as permitted sender) Received: from [209.85.161.172] (HELO mail-gg0-f172.google.com) (209.85.161.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jun 2012 17:19:20 +0000 Received: by ggnc4 with SMTP id c4so4288827ggn.31 for ; Mon, 18 Jun 2012 10:18:59 -0700 (PDT) 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=zIsxxhqXlSWePruUHHuX6AhB/ySgmW7NF6RJM37HEzg=; b=GoIy6aqWKD4we3A+Ju9PUsaAkFpes56sFsGJWqjdWJdy4j3b13pWSFhhuUzZaRtzy3 gyc04gumKES8IPsQgNbVYoNFBB4W4VbTLqc10UkRJBv3jcvKAbnPoGyqhhZmBcNzLsEu NySVIyM8kwdLlQuX7PQCwkEuP9pSTS0AtS6Fo9SDMEm/qG6lIbD4pUZRS0OwTn8PBK8r tSI8v88OVY7eNwf0zCrzCFNL30lBJvaRqhW17G4c5DwDHH2HLjUtx/MtRJNdaHBdAEo9 a+5BrlyuJgJm6E3088OSUkHiuPV+D1tLV3YIZeCjmAi4KYxiqlRXEOuSiHuT5zOkMPcZ wdMA== Received: by 10.236.76.233 with SMTP id b69mr19301474yhe.52.1340039939697; Mon, 18 Jun 2012 10:18:59 -0700 (PDT) MIME-Version: 1.0 Received: by 10.100.195.2 with HTTP; Mon, 18 Jun 2012 10:18:39 -0700 (PDT) From: Cyril Auburtin Date: Mon, 18 Jun 2012 19:18:39 +0200 Message-ID: Subject: large Rows Vs multinodes ring To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=20cf300fb371972ba404c2c25c09 X-Virus-Checked: Checked by ClamAV on apache.org --20cf300fb371972ba404c2c25c09 Content-Type: text/plain; charset=ISO-8859-1 In what extent, having possibly large rows, (many columns (sorted as timeststamp, or geohash or ...) will be nefast for a muli-node ring. I guess a row can be read/write just on one node, if yes it's more likely to fail, (than having one row per timestamp ..) thanks for explanations --20cf300fb371972ba404c2c25c09 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable In what extent, having possibly large rows, (many columns (sorted as timest= stamp, or geohash or ...) will be nefast for a muli-node ring.
I guess = a row can be read/write just on one node, if yes it's more likely to fa= il, (than having one row per timestamp ..)

thanks for explanations
--20cf300fb371972ba404c2c25c09--