[
https://issues.apache.org/jira/browse/CASSANDRA-11387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carl Yeksigian updated CASSANDRA-11387:
---------------------------------------
Resolution: Won't Fix
Status: Resolved (was: Awaiting Feedback)
This would move the read-before-write operation to the server, and would affect
all updates (including ones that don't have a TTL, since we would never know if
they did or not).
This would also break the current contract that TTLs have, which is that the
latest value's TTL is the one used, and an unspecified TTL means use the
table's default TTL.
> If "using ttl" not present in an update statement, ttl shouldn't be updated
> to null
> -----------------------------------------------------------------------------------
>
> Key: CASSANDRA-11387
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11387
> Project: Cassandra
> Issue Type: Improvement
> Components: Core, CQL
> Reporter: Çelebi Murat
> Priority: Minor
>
> When I update a value if I don't use "using ttl = ?", ttl value becomes null
> instead of staying untouched. Thus causing unexpected behaviours. Selecting
> the ttl value of the updated values before the actual update operation is
> hindering both software performance and development speed. Also makes the
> software prone to be buggy.
> Instead, It would be very helpful if the behavior is changed as follows; If
> "using ttl" clause is not present in an update statement, ttl value should
> stay unchanged.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
