cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-5293) formalize that timestamps are epoch-in-micros in 2.0
Date Thu, 07 Mar 2013 16:58:16 GMT


Sylvain Lebresne commented on CASSANDRA-5293:

bq. Didn't we concluded that CASSANDRA-3919 requires that column "timestamp" is a real timestamp?

Yes, but CASSANDRA-3919 is a feature that make sense for CQL3 only. What I mean here is that
I'm fine saying that if you start using CQL3, you should have microseconds timestamps and
CQL3 assumes it, but I think breaking current thrift users is tougher.
> formalize that timestamps are epoch-in-micros in 2.0
> ----------------------------------------------------
>                 Key: CASSANDRA-5293
>                 URL:
>             Project: Cassandra
>          Issue Type: Task
>          Components: Core
>            Reporter: Jonathan Ellis
>             Fix For: 2.0
> We've worked around "don't assume timestamps are actually timestamps" but the utility
is not worth the complexity and lost opportunities to optimize this imposes.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message