cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-11171) conditional update without paxos
Date Mon, 22 Feb 2016 09:43:18 GMT


Sylvain Lebresne commented on CASSANDRA-11171:

Honestly, I'm pretty sure we don't want to do this. It's certainly possible technically, but
the use case feels pretty narrow and on the other side conditions are very much equated to
LWT currently so this would add lots of confusion and potential for foot-shooting. I get that
this would neat for you, but it's also not like we can do magic server side, we'll still have
to do a read-before-write, so we prefer leaving that to the application if that's really what
they want.

> conditional update without paxos
> --------------------------------
>                 Key: CASSANDRA-11171
>                 URL:
>             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 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

View raw message