Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 87266 invoked from network); 10 Apr 2011 02:23:14 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 10 Apr 2011 02:23:14 -0000 Received: (qmail 66060 invoked by uid 500); 10 Apr 2011 02:23:12 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 66037 invoked by uid 500); 10 Apr 2011 02:23:12 -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 66029 invoked by uid 99); 10 Apr 2011 02:23:12 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Apr 2011 02:23:12 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of stuhood@gmail.com designates 209.85.212.171 as permitted sender) Received: from [209.85.212.171] (HELO mail-px0-f171.google.com) (209.85.212.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 10 Apr 2011 02:23:06 +0000 Received: by pxi7 with SMTP id 7so2514978pxi.30 for ; Sat, 09 Apr 2011 19:22:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=0P+4RT/rrDqpIB0NFef+DNmURi0POkhPkN33OdWpM/w=; b=cqWZgG+V+OoEvbaS0EPFMHskbYH2T6v8yJ4F5vX0XZG9yos9HzLhaMnT0mc11kS0+d et4zr22p9nmXSdYTzeyyU0vEc2/oZau3F27aE4/+qjUpLr3UvYpUonfcTUBzvYcuxtuf HVakMVMRLccMSQHoER2/dNiZ6ksVEnlPMxmjI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=i9IHJwZ5PchO+v3WCd3hFv0UWX/V0q3WAAJ4ZA9ow7OB+JUB4qljcG7LeYIKtyXNuM V0LxfL1sQM8cC5oz9hVWGIEw4Mk1osqRHoKG5Wtd/Ux5UNIDu/KwJ9cH5bi0DyBr65d0 6hA3w91B7pxYHS21GChn2w6Qv4m2xe13Gto/o= MIME-Version: 1.0 Received: by 10.142.165.11 with SMTP id n11mr3371086wfe.357.1302402166555; Sat, 09 Apr 2011 19:22:46 -0700 (PDT) Received: by 10.68.65.226 with HTTP; Sat, 9 Apr 2011 19:22:46 -0700 (PDT) In-Reply-To: References: <1302393748191-6257960.post@n2.nabble.com> <3124743461587477655@unknownmsgid> <1302396738637-6258033.post@n2.nabble.com> Date: Sat, 9 Apr 2011 19:22:46 -0700 Message-ID: Subject: Re: Columns values(integer) need frequent updates/ increments From: Stu Hood To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd32d727e032404a0872218 --000e0cd32d727e032404a0872218 Content-Type: text/plain; charset=ISO-8859-1 Sorry, I meant to say #2319: https://issues.apache.org/jira/browse/CASSANDRA-2319 On Sat, Apr 9, 2011 at 6:04 PM, Stu Hood wrote: > If an SSTable contains an update for a row (row, not just column), we need > to read from it. See #1608 for some of the ideas that have been floated on > how to improve this situation: the core ones are 1. partitioning local data > so that the the number of files involved in a read is smaller, 2. adding > support for "superceding" data in older files so that they can be skipped. > #2316 will provide the beginning of a solution to this problem for wide > rows. > > > On Sat, Apr 9, 2011 at 5:52 PM, mcasandra wrote: > >> That I understand but my basic quesiton was how does it know that there >> are >> multiple updates that have occurred on the same column? and how does it >> efficiently knows which sstable have these updates? >> >> -- >> View this message in context: >> http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Columns-values-integer-need-frequent-updates-increments-tp6251464p6258033.html >> Sent from the cassandra-user@incubator.apache.org mailing list archive at >> Nabble.com. >> > > --000e0cd32d727e032404a0872218 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sorry, I meant to say #2319:=A0https://issues.apache.org/jira/browse/CASSANDRA-2319

On Sat, Apr 9, 2011 at 6:04 PM, Stu Ho= od <stuhood@gmail= .com> wrote:
If an SSTable contains an update for a row = (row, not just column), we need to read from it. See #1608 for some of the = ideas that have been floated on how to improve this situation: the core one= s are 1. partitioning local data so that the the number of files involved i= n a read is smaller, 2. adding support for "superceding" data in = older files so that they can be skipped. #2316 will provide the beginning o= f a solution to this problem for wide rows.


On Sat, Apr 9, 2011 at 5:52 PM, mcasandr= a <mohitanchlia@gmail.com> wrote:
That I understand but my basic quesiton was how does it know that there are=
multiple updates that have occurred on the same column? and how does it
efficiently knows which sstable have these updates?

--
View this message in context: http://cassandra-user= -incubator-apache-org.3065146.n2.nabble.com/Columns-values-integer-need-fre= quent-updates-increments-tp6251464p6258033.html
Sent from the cassandra-user@incubator.apache.org= mailing list archive at Nabble.com.


--000e0cd32d727e032404a0872218--