[jira] [Updated] (CASSANDRA-8246) Default timestamp for QueryOptions should be Long.MIN_VALUE

["Sam Tunnicliffe (JIRA)" <ji...@apache.org>]

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

Sam Tunnicliffe updated CASSANDRA-8246:
---------------------------------------
    Attachment: 8246.txt

Attached patch is a one liner to fix the default value, plus a unit test using {{QueryProcessor.instance.process}} to illustrate the problem (the test may be overkill).

> Default timestamp for QueryOptions should be Long.MIN_VALUE
> -----------------------------------------------------------
>
>                 Key: CASSANDRA-8246
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8246
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>             Fix For: 2.1.2
>
>         Attachments: 8246.txt
>
>
> CASSANDRA-8139 adds proper handling for negative timestamps, but one case was missed in the merge to cassandra-2.1.
> {{QueryOptions.SpecificOptions.DEFAULT}} is still created with a timestamp of -1, so statements which do not come in via the native protocol will retain this timestamp and not be assigned a server-side timestamp at execution time.{{QueryOptions.Codec}} does the right thing, so statements that do come via the protocol are unaffected.



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