You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by Jeff Zhang <zj...@gmail.com> on 2010/04/22 09:56:15 UTC
Does anybody work about transaction on cassandra ?
Hi all,
I need transaction support on cassandra, so wondering is anybody work on it ?
--
Best Regards
Jeff Zhang
Re: Does anybody work about transaction on cassandra ?
Posted by Mason Hale <ma...@onespot.com>.
You might also consider using a Software Transactional Memory[1] approach. I
haven't personally tried it, but there is a Scala/Java framework named Akka
that provides both STM features and Cassandra support. Should be worth a
look. Here's a nice write-up from someone who has already done some
exploring: http://codemonkeyism.com/cassandra-scala-akka/
[1] http://en.wikipedia.org/wiki/Software_transactional_memory
[2] http://doc.akkasource.org/
Mason Hale
http://www.onespot.com
On Thu, Apr 22, 2010 at 9:14 AM, Miguel Verde <mi...@gmail.com>wrote:
> No, as far as I know no one is working on transaction support in
> Cassandra. Transactions are orthogonal to the design of Cassandra[1][2],
> although a system could be designed incorporating Cassandra and other
> elements a la Google's MegaStore[3] to support transactions. Google uses
> Paxos, one might be able to use Zookeeper[4] to design such a system, but it
> would be a daunting task.
>
> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
> [2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
> [4] http://hadoop.apache.org/zookeeper/
>
> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
>
>> Hi all,
>>
>> I need transaction support on cassandra, so wondering is anybody work on
>> it ?
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>
Re: Does anybody work about transaction on cassandra ?
Posted by dir dir <si...@gmail.com>.
>No, it just means they don't have dependencies on each other. In this
>case, it means you could create a transactional layer on top of
>cassandra, without having to make it part of the core.
Now I Understand, thank you.
On Sun, Apr 25, 2010 at 12:46 AM, Jonathan Ellis <jb...@gmail.com> wrote:
> On Sat, Apr 24, 2010 at 12:44 PM, Benoit Perroud <be...@noisette.ch>
> wrote:
> > "orthogonal" means "90 degrees". Two lines are orthogonal if the
> > cross at 90 degrees.
> >
> > Two ideas are orthogonal means that they are not compatible.
>
> No, it just means they don't have dependencies on each other. In this
> case, it means you could create a transactional layer on top of
> cassandra, without having to make it part of the core.
>
Re: Does anybody work about transaction on cassandra ?
Posted by Benoit Perroud <be...@noisette.ch>.
Ok in this particular context it means no dependencies.
Thanks for your precision.
Kind regards,
Benoit.
2010/4/24 Jonathan Ellis <jb...@gmail.com>:
> On Sat, Apr 24, 2010 at 12:44 PM, Benoit Perroud <be...@noisette.ch> wrote:
>> "orthogonal" means "90 degrees". Two lines are orthogonal if the
>> cross at 90 degrees.
>>
>> Two ideas are orthogonal means that they are not compatible.
>
> No, it just means they don't have dependencies on each other. In this
> case, it means you could create a transactional layer on top of
> cassandra, without having to make it part of the core.
>
Re: Does anybody work about transaction on cassandra ?
Posted by Jonathan Ellis <jb...@gmail.com>.
On Sat, Apr 24, 2010 at 12:44 PM, Benoit Perroud <be...@noisette.ch> wrote:
> "orthogonal" means "90 degrees". Two lines are orthogonal if the
> cross at 90 degrees.
>
> Two ideas are orthogonal means that they are not compatible.
No, it just means they don't have dependencies on each other. In this
case, it means you could create a transactional layer on top of
cassandra, without having to make it part of the core.
Re: Does anybody work about transaction on cassandra ?
Posted by Benoit Perroud <be...@noisette.ch>.
"orthogonal" means "90 degrees". Two lines are orthogonal if the
cross at 90 degrees.
Two ideas are orthogonal means that they are not compatible.
Transactions is orthogonal with Cassandra's design means that it will
require a lot of work and trade-off to implement transactions into
Cassandra.
Is it more clear ?
Kind regards,
Benoit
2010/4/24 dir dir <si...@gmail.com>:
> Do you mean orthogonal like Commit and Rollback?? For example after we
> perform Rollback, hence we cannot going back.
>
>>Including "transaction" in Cassandra needs to turn 90 degrees
>>the design of Cassandra
>
> I do not understand what is the meaning of "needs to turn 90 degrees"??
>
> Thank you.
>
> On Sun, Apr 25, 2010 at 12:30 AM, Benoit Perroud <be...@noisette.ch> wrote:
>>
>> "orthogonal" means "go to the opposite direction, but without going
>> back". Including "transaction" in Cassandra needs to turn 90 degrees
>> the design of Cassandra.
>>
>> Kind regards,
>>
>> Benoit.
>>
>>
>>
>> 2010/4/24 dir dir <si...@gmail.com>:
>> >>Transactions are orthogonal to the design of Cassandra
>> >
>> > Sorry, Would you want to tell me what is an orthogonal mean in this
>> > context??
>> > honestly I do not understand what is it.
>> >
>> > Thank you.
>> >
>> >
>> > On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com>
>> > wrote:
>> >>
>> >> No, as far as I know no one is working on transaction support in
>> >> Cassandra. Transactions are orthogonal to the design of
>> >> Cassandra[1][2],
>> >> although a system could be designed incorporating Cassandra and other
>> >> elements a la Google's MegaStore[3] to support transactions. Google
>> >> uses
>> >> Paxos, one might be able to use Zookeeper[4] to design such a system,
>> >> but it
>> >> would be a daunting task.
>> >>
>> >> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
>> >> [2]
>> >> http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
>> >> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
>> >> [4] http://hadoop.apache.org/zookeeper/
>> >>
>> >> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
>> >>>
>> >>> Hi all,
>> >>>
>> >>> I need transaction support on cassandra, so wondering is anybody work
>> >>> on
>> >>> it ?
>> >>>
>> >>>
>> >>> --
>> >>> Best Regards
>> >>>
>> >>> Jeff Zhang
>> >>
>> >
>> >
>
>
Re: Does anybody work about transaction on cassandra ?
Posted by dir dir <si...@gmail.com>.
Do you mean orthogonal like Commit and Rollback?? For example after we
perform Rollback, hence we cannot going back.
>Including "transaction" in Cassandra needs to turn 90 degrees
>the design of Cassandra
I do not understand what is the meaning of "needs to turn 90 degrees"??
Thank you.
On Sun, Apr 25, 2010 at 12:30 AM, Benoit Perroud <be...@noisette.ch> wrote:
> "orthogonal" means "go to the opposite direction, but without going
> back". Including "transaction" in Cassandra needs to turn 90 degrees
> the design of Cassandra.
>
> Kind regards,
>
> Benoit.
>
>
>
> 2010/4/24 dir dir <si...@gmail.com>:
> >>Transactions are orthogonal to the design of Cassandra
> >
> > Sorry, Would you want to tell me what is an orthogonal mean in this
> > context??
> > honestly I do not understand what is it.
> >
> > Thank you.
> >
> >
> > On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com>
> > wrote:
> >>
> >> No, as far as I know no one is working on transaction support in
> >> Cassandra. Transactions are orthogonal to the design of
> Cassandra[1][2],
> >> although a system could be designed incorporating Cassandra and other
> >> elements a la Google's MegaStore[3] to support transactions. Google
> uses
> >> Paxos, one might be able to use Zookeeper[4] to design such a system,
> but it
> >> would be a daunting task.
> >>
> >> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
> >> [2]
> http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
> >> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
> >> [4] http://hadoop.apache.org/zookeeper/
> >>
> >> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> I need transaction support on cassandra, so wondering is anybody work
> on
> >>> it ?
> >>>
> >>>
> >>> --
> >>> Best Regards
> >>>
> >>> Jeff Zhang
> >>
> >
> >
>
Re: Does anybody work about transaction on cassandra ?
Posted by Benoit Perroud <be...@noisette.ch>.
"orthogonal" means "go to the opposite direction, but without going
back". Including "transaction" in Cassandra needs to turn 90 degrees
the design of Cassandra.
Kind regards,
Benoit.
2010/4/24 dir dir <si...@gmail.com>:
>>Transactions are orthogonal to the design of Cassandra
>
> Sorry, Would you want to tell me what is an orthogonal mean in this
> context??
> honestly I do not understand what is it.
>
> Thank you.
>
>
> On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com>
> wrote:
>>
>> No, as far as I know no one is working on transaction support in
>> Cassandra. Transactions are orthogonal to the design of Cassandra[1][2],
>> although a system could be designed incorporating Cassandra and other
>> elements a la Google's MegaStore[3] to support transactions. Google uses
>> Paxos, one might be able to use Zookeeper[4] to design such a system, but it
>> would be a daunting task.
>>
>> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
>> [2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
>> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
>> [4] http://hadoop.apache.org/zookeeper/
>>
>> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
>>>
>>> Hi all,
>>>
>>> I need transaction support on cassandra, so wondering is anybody work on
>>> it ?
>>>
>>>
>>> --
>>> Best Regards
>>>
>>> Jeff Zhang
>>
>
>
Re: Does anybody work about transaction on cassandra ?
Posted by Cagatay Kavukcuoglu <ca...@kavukcuoglu.org>.
Better fault tolerance? Scalability to large data volumes? A combination of ZooKeeper based transactions and Cassandra may have better characteristics than RDBMS on these criteria. There's no question that trade-offs are involved, but as far as these issues are concerned, you'd be starting from a better vantage point than a SPOF relational database.
On Apr 26, 2010, at 10:24 AM, Mark Jones wrote:
> Orthogonal in this case means “at cross purposes” Transactions can’t really be done with eventual consistency because all nodes don’t have all the info at the time the transaction is done. I think they recommend zookeeper for this kind of stuff, but I don’t know why you want to use Cassandra vs a RDBMS if you really want transactions.
>
> From: dir dir [mailto:sikerasakti@gmail.com]
> Sent: Saturday, April 24, 2010 12:08 PM
> To: user@cassandra.apache.org
> Subject: Re: Does anybody work about transaction on cassandra ?
>
> >Transactions are orthogonal to the design of Cassandra
>
> Sorry, Would you want to tell me what is an orthogonal mean in this context??
> honestly I do not understand what is it.
>
> Thank you.
>
>
> On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com> wrote:
> No, as far as I know no one is working on transaction support in Cassandra. Transactions are orthogonal to the design of Cassandra[1][2], although a system could be designed incorporating Cassandra and other elements a la Google's MegaStore[3] to support transactions. Google uses Paxos, one might be able to use Zookeeper[4] to design such a system, but it would be a daunting task.
>
> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
> [2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
> [4] http://hadoop.apache.org/zookeeper/
>
> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
> Hi all,
>
> I need transaction support on cassandra, so wondering is anybody work on it ?
>
>
> --
> Best Regards
>
> Jeff Zhang
>
>
RE: Does anybody work about transaction on cassandra ?
Posted by Mark Jones <MJ...@imagehawk.com>.
Orthogonal in this case means "at cross purposes" Transactions can't really be done with eventual consistency because all nodes don't have all the info at the time the transaction is done. I think they recommend zookeeper for this kind of stuff, but I don't know why you want to use Cassandra vs a RDBMS if you really want transactions.
From: dir dir [mailto:sikerasakti@gmail.com]
Sent: Saturday, April 24, 2010 12:08 PM
To: user@cassandra.apache.org
Subject: Re: Does anybody work about transaction on cassandra ?
>Transactions are orthogonal to the design of Cassandra
Sorry, Would you want to tell me what is an orthogonal mean in this context??
honestly I do not understand what is it.
Thank you.
On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com>> wrote:
No, as far as I know no one is working on transaction support in Cassandra. Transactions are orthogonal to the design of Cassandra[1][2], although a system could be designed incorporating Cassandra and other elements a la Google's MegaStore[3] to support transactions. Google uses Paxos, one might be able to use Zookeeper[4] to design such a system, but it would be a daunting task.
[1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
[2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
[3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
[4] http://hadoop.apache.org/zookeeper/
On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com>> wrote:
Hi all,
I need transaction support on cassandra, so wondering is anybody work on it ?
--
Best Regards
Jeff Zhang
Re: Does anybody work about transaction on cassandra ?
Posted by dir dir <si...@gmail.com>.
>Transactions are orthogonal to the design of Cassandra
Sorry, Would you want to tell me what is an orthogonal mean in this
context??
honestly I do not understand what is it.
Thank you.
On Thu, Apr 22, 2010 at 9:14 PM, Miguel Verde <mi...@gmail.com>wrote:
> No, as far as I know no one is working on transaction support in
> Cassandra. Transactions are orthogonal to the design of Cassandra[1][2],
> although a system could be designed incorporating Cassandra and other
> elements a la Google's MegaStore[3] to support transactions. Google uses
> Paxos, one might be able to use Zookeeper[4] to design such a system, but it
> would be a daunting task.
>
> [1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
> [2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
> [3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
> [4] http://hadoop.apache.org/zookeeper/
>
> On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
>
>> Hi all,
>>
>> I need transaction support on cassandra, so wondering is anybody work on
>> it ?
>>
>>
>> --
>> Best Regards
>>
>> Jeff Zhang
>>
>
>
Re: Does anybody work about transaction on cassandra ?
Posted by Miguel Verde <mi...@gmail.com>.
No, as far as I know no one is working on transaction support in Cassandra.
Transactions are orthogonal to the design of Cassandra[1][2], although a
system could be designed incorporating Cassandra and other elements a la
Google's MegaStore[3] to support transactions. Google uses Paxos, one might
be able to use Zookeeper[4] to design such a system, but it would be a
daunting task.
[1] http://www.julianbrowne.com/article/viewer/brewers-cap-theorem
[2] http://www.allthingsdistributed.com/2008/12/eventually_consistent.html
[3] http://perspectives.mvdirona.com/2008/07/10/GoogleMegastore.aspx
[4] http://hadoop.apache.org/zookeeper/
On Thu, Apr 22, 2010 at 2:56 AM, Jeff Zhang <zj...@gmail.com> wrote:
> Hi all,
>
> I need transaction support on cassandra, so wondering is anybody work on it
> ?
>
>
> --
> Best Regards
>
> Jeff Zhang
>