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 Tue, 02 Apr 2013 17:09:16 GMT


Sylvain Lebresne commented on CASSANDRA-5293:

Just to clarity on what my opinion is here, I guess I'm just asking what is the actual suggestion
in practice. I'm absolutely fine saying that from now on, new features might assume that timestamps
are epoch-in-micros, and that user should update to that convention to use new features (CASSANDRA-3919
being one such feature, CASSANDRA-5062 being another one).

But I'd rather avoid retro-fitting that new assumption in old code, and make tombstones deletion
based on the client timestamp instead of the localDeletionTime. Again, maybe that wasn't part
of the suggestion. But if that was, I think that's a bit too harsh. Again, even if people
epoch-in-milliseconds, moving to epoch-in-microseconds is costly. And there is people using
epoch-in-nanoseconds (see CASSANDRA-5412) for which it would be *very* costly.
> 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