[
https://issues.apache.org/jira/browse/CASSANDRA-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14178673#comment-14178673
]
Tyler Hobbs commented on CASSANDRA-8139:
----------------------------------------
bq. it's true technically that we don't forbid negative timestamps so I suppose
we should either start forbidding them or fix this, and it's probably easier to
just fix this so attaching a simple patch.
At least for the v3 protocol, we explicitly disallow negative timestamps. See
the discussion on CASSANDRA-6855 (and this commit in particular:
https://github.com/pcmanus/cassandra/commit/d9a584efa94b9c3deb35746985a45573f16bb9bd).
> The WRITETIME function returns null for negative timestamp values
> -----------------------------------------------------------------
>
> Key: CASSANDRA-8139
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8139
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Richard Bremner
> Assignee: Sylvain Lebresne
> Priority: Minor
> Fix For: 2.0.12
>
> Attachments: 8139.txt
>
>
> Insert a column with a negative timestamp value:
> {code}
> INSERT INTO my_table (col1, col2, col3)
> VALUES ('val1', 'val2', 'val3')
> USING TIMESTAMP -1413614886750020;
> {code}
> Then attempt to read the *writetime*:
> {code}
> SELECT WRITETIME(col3) FROM my_table WHERE col1 = 'val1'
> {code}
> The result is *null*.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
