[
https://issues.apache.org/jira/browse/CASSANDRA-8139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14179871#comment-14179871
]
Sylvain Lebresne commented on CASSANDRA-8139:
---------------------------------------------
Oh right, forgot about that. Well, I suppose that mean we have started
forbidding them. But anyway, for 2.0, I still think the patch stands. Even if
we do refuse negative timestamps in the protocol v3, we can't totally guarantee
that there won't be some pre-existing ones so better safe than sorry. It would
probably make ense to start refusing negative timestamps more generally on the
CQL side, but I'd rather not do that in a minor release, so I'll open a
separate ticket for it.
> 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)
