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 38A2275B0 for ; Thu, 6 Oct 2011 18:50:49 +0000 (UTC) Received: (qmail 83175 invoked by uid 500); 6 Oct 2011 18:50:47 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 83143 invoked by uid 500); 6 Oct 2011 18:50:47 -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 83135 invoked by uid 99); 6 Oct 2011 18:50:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 18:50:47 +0000 X-ASF-Spam-Status: No, hits=-0.6 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_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 ramesh25@gmail.com designates 209.85.210.172 as permitted sender) Received: from [209.85.210.172] (HELO mail-iy0-f172.google.com) (209.85.210.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Oct 2011 18:50:39 +0000 Received: by iaby26 with SMTP id y26so4034231iab.31 for ; Thu, 06 Oct 2011 11:50:18 -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=2Os8ThvReMMRuw2GPCeZWhcAh1GtyLn6XRkqX5/duTo=; b=nb6g9g4SkkmKGekq1tD6ZsHytuF0A8LcV0TgWEaqJsFlPvz/Z5EXCspNA7P1XHccl0 mFlph3PzudL9JHMDuyUY02DjYDGn2JefLP5cCbl90lNMH08AyOs/lIm9cWcqNovpdSHs fuUeIr0E6OkTXC4Q54zpy2xm5OS+jkkxVg/RY= MIME-Version: 1.0 Received: by 10.42.243.138 with SMTP id lm10mr6506957icb.6.1317927018331; Thu, 06 Oct 2011 11:50:18 -0700 (PDT) Received: by 10.42.225.198 with HTTP; Thu, 6 Oct 2011 11:50:17 -0700 (PDT) Date: Thu, 6 Oct 2011 13:50:17 -0500 Message-ID: Subject: read on multiple SS tables From: Ramesh Natarajan To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Lets assume I perform frequent insert & update on a column family.. Over a period of time multiple sstables will have this row/column data. I have 2 questions about how reads work in cassandra w.r.t. multiple SS tables. -If you perform a query for a specific row key and a column name, does it read the most recent SSTable first and if it finds a hit, does it stop there or does it need to read through all the SStables (to find most recent one) regardless of whether if found a hit on the most recent SSTable or not? - If I perform a slice query on a column range does cassandra iterate all the SS tables? We have an option to create 1st option: Key1 | COL1 | COL2 | COL3 ..... We need to perform a slice query to get COL1-COL3 using key1. 2nd option: Key1 | This key would be updated several times where the app would manage adding multiple values to the one column key. Our max col value size will be less than 64mb. When you need to search for a value, we would read the one column and the application would manage looking up the appropriate value in the list of values. So I am wondering which option would be most efficient from read point of view. thanks Ramesh