cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11171) conditional update without paxos
Date Thu, 14 Dec 2017 03:50:00 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16290298#comment-16290298
] 

Jeff Jirsa commented on CASSANDRA-11171:
----------------------------------------

It's been a few years, and it feels like this is something that is almost certainly not going
to be implemented. I propose wont-fixing this, will label it as such, and close it later unless
someone objects.

> 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
>              Labels: proposed-wontfix
>
> I realise that currently conditional updates use lightweight transactions to provide
an atomic check and set operation 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.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org


Mime
View raw message