cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anonymous (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-11387) If "using ttl" not present in an update statement, ttl shouldn't be updated to null
Date Thu, 24 Mar 2016 10:08:25 GMT

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

Anonymous updated CASSANDRA-11387:
----------------------------------
    Reproduced In: 3.3
           Status: Awaiting Feedback  (was: Open)

> 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)

Mime
View raw message