Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 58110 invoked from network); 7 Sep 2010 07:08:25 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 7 Sep 2010 07:08:25 -0000 Received: (qmail 76797 invoked by uid 500); 7 Sep 2010 07:08:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 76667 invoked by uid 500); 7 Sep 2010 07:08:21 -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 76659 invoked by uid 99); 7 Sep 2010 07:08:20 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 07:08:20 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of augustyn.michal@gmail.com designates 209.85.216.179 as permitted sender) Received: from [209.85.216.179] (HELO mail-qy0-f179.google.com) (209.85.216.179) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Sep 2010 07:07:57 +0000 Received: by qyk9 with SMTP id 9so5006941qyk.10 for ; Tue, 07 Sep 2010 00:07:37 -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=ToIjFmdSPjMfuqcQsrpAle5RTceEIZWiMMqoaOkvhb4=; b=JF2iJY8HDK/0DJ9uimO4TBx+aJ59/kIIeegzN+RHeaCFxy3ndO4m4UOthlxUTLXW5R UdtvYj680KQzvdMi9PaiP3twJI2ipydL5sM6M6lLz4B5FzC1OHQZOfSjcAKQZGZ65r4m ipI+VmOx3Jz76i+o1KeeifO/i0nBMPNWCxxyY= 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=Fk1UUE+UZxSqxrM8rHaq6/AGYQZY2BLjMHbVMXHCu5mKn3eRVMg966AIIQjcXdmZ4R FoZTgNis4AVk9EX0Ka4VijkVDC2zRDrs6NdYA6WKmzLzzGYom9XKS8HSHxffCY77DY6S PnhCuvCm/o0KoG0PeXlCUVRkglIpmaWsM5bHA= MIME-Version: 1.0 Received: by 10.229.213.200 with SMTP id gx8mr4323654qcb.89.1283843257014; Tue, 07 Sep 2010 00:07:37 -0700 (PDT) Received: by 10.229.25.144 with HTTP; Tue, 7 Sep 2010 00:07:35 -0700 (PDT) In-Reply-To: References: Date: Tue, 7 Sep 2010 09:07:35 +0200 Message-ID: Subject: Re: How to implement (generic) ACID on application level From: =?ISO-8859-1?Q?Michal_August=FDn?= To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=0016361e87644819ea048fa60d71 X-Virus-Checked: Checked by ClamAV on apache.org --0016361e87644819ea048fa60d71 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Never mind - I didn't want to send the last paragraph. I'm sorry. 2010/9/7 Jonathan Shook > ... some kind of what? > > On Mon, Sep 6, 2010 at 3:38 AM, Michal August=FDn > wrote: > > Thank you for the great link! > > The mentioned solution is using locking but I would prefer some > optimistic > > strategy (because the conflicts are rare in my situation) but I'm afrai= d > > that this is really the best solution... > > So the solution is probably to use some kind of > > 2010/9/6 Reza Lesmana > >> > >> I read an article about using CAGES with Cassandra to achieve locking > >> and transaction... > >> > >> Here is the link : > >> > >> > >> > http://ria101.wordpress.com/2010/05/12/locking-and-transactions-over-cass= andra-using-cages/ > >> > >> On 9/5/10, Michal August=FDn wrote: > >> > Hello, > >> > > >> > we can read everywhere that Cassandra (and similar NoSQL solutions) > >> > doesn't > >> > support full ACID and (when we want to have ACID) we have to impleme= nt > >> > ACID > >> > in higher layers of our application. Are there some good resources o= n > >> > how to > >> > implement ACID on higher layers? I.e. how to implement repository > >> > pattern/DAO with ACID support when Cassandra is the database. > >> > > >> > I'm sure that some pessimistic solution (locks) is absolutely > unsuitable > >> > for > >> > Cassandra so the solution probably would deal with optimistic > >> > concurrency... > >> > > >> > Thank you! > >> > > >> > Augi > >> > > > > > > --0016361e87644819ea048fa60d71 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Never mind - I didn't want to send the last paragraph. I'm sorry.
2010/9/7 Jonathan Shook = <jshook@gmail.com>
=
... some kind of what?

On Mon, Sep 6, 2010 at 3:38 AM, Michal August=FDn
<augustyn.michal@gmail.com> wrote:
> Thank you for the great link!
> The mentioned solution is using locking but I would prefer some optimi= stic
> strategy (because the conflicts are rare in my situation) but I'm = afraid
> that this is really the best solution...
> So the solution is probably to use some kind of
> 2010/9/6 Reza Lesmana <le= smana.reza@gmail.com>
>>
>> I read an article about using CAGES with Cassandra to achieve lock= ing
>> and transaction...
>>
>> Here is the link :
>>
>>
>> http://ria101.wordp= ress.com/2010/05/12/locking-and-transactions-over-cassandra-using-cages/
>>
>> On 9/5/10, Michal August=FDn <augustyn.michal@gmail.com> wrote:
>> > Hello,
>> >
>> > we can read everywhere that Cassandra (and similar NoSQL solu= tions)
>> > doesn't
>> > support full ACID and (when we want to have ACID) we have to = implement
>> > ACID
>> > in higher layers of our application. Are there some good reso= urces on
>> > how to
>> > implement ACID on higher layers? I.e. how to implement reposi= tory
>> > pattern/DAO with ACID support when Cassandra is the database.=
>> >
>> > I'm sure that some pessimistic solution (locks) is absolu= tely unsuitable
>> > for
>> > Cassandra so the solution probably would deal with optimistic=
>> > concurrency...
>> >
>> > Thank you!
>> >
>> > Augi
>> >
>
>

--0016361e87644819ea048fa60d71--