Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cassandra-user@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 209.85.218.210 as permitted sender)
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=xstjdDz1+64HRTmRGCaaXDqNb2VbaWajS1XGBciG2t1njVg1+tp3587SPD64bzB8c4
         FAPbPbdkIGNl3Yq2JJuBuauBCx/WQDvtMk1VoFMGB3bcaQoFOz/qOQvgse5Ae35WASTh
         Lowzns/FTUSQoay1FxVgC5M3hiKEzV3mx9518=
MIME-Version: 1.0
In-Reply-To: <828083e70912111132r3fb877bam9bbf2a0f8108df52@mail.gmail.com>
References: <9972cc9e0912110927n35a60dc3m1db5efc78ab7df7f@mail.gmail.com>
	<828083e70912111132r3fb877bam9bbf2a0f8108df52@mail.gmail.com>
From: Jonathan Ellis <jbellis@gmail.com>
Date: Fri, 11 Dec 2009 13:42:44 -0600
Message-ID: <e06563880912111142m5aaff987hbd6a8d7d68db357d@mail.gmail.com>
Subject: Re: Questions about optmizing interaction with Cassandra
To: cassandra-user@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Dec 11, 2009 at 1:32 PM, gabriele renzi <rff.rff@gmail.com> wrote:
> FWIW, in our current application with 0.4 we implemented in-cassandra
> caching, whereas a query that reads many thousands of columns and
> takes some time is cached in a separate entry
> QueryCache[q]=serializedResult
> and we flush it on update.
> I don't see why that cant be done by cassandra itself (maybe it's
> already done in 0.5)

No, but it is worth exploring.

-Jonathan