You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Nils Kilden-Pedersen (JIRA)" <ji...@apache.org> on 2015/01/25 05:00:35 UTC

[jira] [Updated] (CASSANDRA-8679) Successful LWT INSERT should return any server generated values

     [ https://issues.apache.org/jira/browse/CASSANDRA-8679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nils Kilden-Pedersen updated CASSANDRA-8679:
--------------------------------------------
    Description: 
A failed LWT INSERT returns the row that prevented insertion, along with {{[applied]}} boolean value. A successful LWT INSERT only returns {{[applied]}}.
It would be helpful to also return any other server generated values, e.g. {{NOW()}} as {{[now]}} (or whatever).
There is currently no way to know what exactly was inserted without re-querying the row, which is horrible for write-throughput.

  was:
A failed LWT INSERT returns the row that prevented insertion, along with `[applied]` boolean value. A successful LWT INSERT only returns `[applied]`.
It would be helpful to also return any other server generated values, e.g. `NOW()` as `[now]` (or whatever).
There is currently no way to know what exactly was inserted without re-querying the row, which is horrible for write-throughput.


> Successful LWT INSERT should return any server generated values
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-8679
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8679
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Nils Kilden-Pedersen
>
> A failed LWT INSERT returns the row that prevented insertion, along with {{[applied]}} boolean value. A successful LWT INSERT only returns {{[applied]}}.
> It would be helpful to also return any other server generated values, e.g. {{NOW()}} as {{[now]}} (or whatever).
> There is currently no way to know what exactly was inserted without re-querying the row, which is horrible for write-throughput.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)