: 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 i
you want to use Cassandra vs a RDBMS if you
really want transactions.
From: dir dir [mailto:sikerasa...@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
>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 wrote:
> On Sat, Apr 24
Ok in this particular context it means no dependencies.
Thanks for your precision.
Kind regards,
Benoit.
2010/4/24 Jonathan Ellis :
> On Sat, Apr 24, 2010 at 12:44 PM, Benoit Perroud wrote:
>> "orthogonal" means "90 degrees". Two lines are orthogonal if the
>> cross at 90 degrees.
>>
>> Two
On Sat, Apr 24, 2010 at 12:44 PM, Benoit Perroud 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
"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.
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,
"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 :
>>Transactions are orthogonal to the design of Cassandra
>
> Sorry, Would you want to tell
>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 wrote:
> No, as far as I know no one is working on transaction
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
explo
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
Hi all,
I need transaction support on cassandra, so wondering is anybody work on it ?
--
Best Regards
Jeff Zhang
12 matches
Mail list logo