[
https://issues.apache.org/jira/browse/CASSANDRA-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stuart updated CASSANDRA-11171:
-------------------------------
Description: I realise that currently conditional updates use lightweight
transactions to provide an atomic check and set operation for conditional
updates but that this comes at a non trivial performance cost. I have a
solution where synchronised access is ensured by an external mechanism
therefore I don't think paxos would be required. It would be nice to be able to
run an update command or script that could conditionally update without the
performance hit. Currently I'd have to retrieve each row first at the
application level before deciding whether or not to perform the update. Would
it be possible to add a switch for the conditional updates to turn paxos on or
off? Thanks. (was: I realise that currently conditional updates use
lightweight transactions to provide an atomic check and set operation for
conditional updates but that this comes at a non trivial performance cost. I
have a solution where synchronised access is ensured by an external mechanism
therefore I don't think paxos would be required. It would be nice to be able to
run an update command or script that could conditionally update without the
performance hit. Currently I'd have to retrieve each row first at the
application level before deciding whether or not to perform the update. Would
it be possible to add a switch for the conditional update to turn paxos on or
off? Thanks.)
> conditional update without paxos
> --------------------------------
>
> Key: CASSANDRA-11171
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11171
> Project: Cassandra
> Issue Type: Wish
> Reporter: stuart
> Priority: Minor
>
> I realise that currently conditional updates use lightweight transactions to
> provide an atomic check and set operation for conditional updates but that
> this comes at a non trivial performance cost. I have a solution where
> synchronised access is ensured by an external mechanism therefore I don't
> think paxos would be required. It would be nice to be able to run an update
> command or script that could conditionally update without the performance
> hit. Currently I'd have to retrieve each row first at the application level
> before deciding whether or not to perform the update. Would it be possible to
> add a switch for the conditional updates to turn paxos on or off? Thanks.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
