Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 78065 invoked from network); 4 May 2010 11:28:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 May 2010 11:28:45 -0000 Received: (qmail 95656 invoked by uid 500); 4 May 2010 11:28:44 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 95606 invoked by uid 500); 4 May 2010 11:28:43 -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 95598 invoked by uid 99); 4 May 2010 11:28:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 11:28:42 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of vineetdaniel@gmail.com designates 74.125.83.44 as permitted sender) Received: from [74.125.83.44] (HELO mail-gw0-f44.google.com) (74.125.83.44) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 May 2010 11:28:35 +0000 Received: by gwaa12 with SMTP id a12so1691018gwa.31 for ; Tue, 04 May 2010 04:28:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=MWNM9j+YAIVzwwQNFokf9K5vEkhMg/4rfWORV9bSCos=; b=DHMrhXjXLZT0Lm9oBNtomBBdU5H9fU+Nkk0iNe/bFw3rjWZ6k6Ez3yF/+KeHEa84Sc i6h0NrUfBmKBrVv3zebYpe4kbS9lJntd0DdK6yRMUgjVPc3LdGODXrWCAZgZP2xHkc/p YEgZR4Og6AhZl7GRofcH4RFsAJlxg39W+Ikqg= 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=fTRgDOzip3rdFODNGVlLOBNjJ/1Lw9BWyYRRwGOqdop9qBOEB2ojTB5vxH+HHxrZWm al+0dpCheoKeG36g7rORrLsvG4FM6mCaRvtdly1smPjFCnglPeEMo8CBlW3gO6fJjMrs DA4YFU8+Hgm4xHmowX4G+Ii7Lqkq7fEJXmThA= MIME-Version: 1.0 Received: by 10.150.209.1 with SMTP id h1mr11050463ybg.203.1272972494042; Tue, 04 May 2010 04:28:14 -0700 (PDT) Received: by 10.150.229.11 with HTTP; Tue, 4 May 2010 04:28:14 -0700 (PDT) In-Reply-To: References: Date: Tue, 4 May 2010 16:58:14 +0530 Message-ID: Subject: Re: how to fetch latest data From: vineet daniel To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=000e0cd51c9e50f7910485c30112 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd51c9e50f7910485c30112 Content-Type: text/plain; charset=UTF-8 If R + W > N, where R, W, and N are respectively the read replica count, the write replica count, and the replication factor, all client reads will see the most recent write. On Tue, May 4, 2010 at 4:39 PM, vineet daniel wrote: > Hi > > In a cluster of cassandra if we are updating any key/value and perform the > fetch query on that same key, we get old/stale data. This can be because of > Read Repair. > > Is there any way to fetch the latest updated data from the cluster, as old > data stands no significance and showing it to client is more irrelevant. > > Regards > Vineet Daniel > --000e0cd51c9e50f7910485c30112 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable If R + W > N, where R, W, and N are respectively the read replica count,= the write replica count, and the replication factor, all client reads will= see the most recent write.

On Tue, May 4= , 2010 at 4:39 PM, vineet daniel <vineetdaniel@gmail.com> wrote:
Hi

In a cl= uster of cassandra if we are updating any key/value and perform the fetch q= uery on that same key, we get old/stale data. This can be because of Read R= epair.

Is there any way to fetch the latest updated data from the cluster, as = old data stands no significance and showing it to client is more irrelevant= .

Regards
Vineet Daniel

--000e0cd51c9e50f7910485c30112--