You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Çelebi Murat (JIRA)" <ji...@apache.org> on 2016/03/21 11:42:25 UTC
[jira] [Created] (CASSANDRA-11387) If "using ttl" not present in an
update statement, ttl shouldn't be updated to null
Çelebi Murat created CASSANDRA-11387:
----------------------------------------
Summary: 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)