[ 
https://issues.apache.org/jira/browse/CASSANDRA-7919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14132810#comment-14132810
 ] 

Benedict edited comment on CASSANDRA-7919 at 9/13/14 4:17 PM:
--------------------------------------------------------------

That is stale info, unfortunately :)

If we correct the risk of collision within a single application server, which 
is pretty essential, our LSB will suddenly explode regardless of how static our 
client set-of-ips is so optimising storage becomes impossible. And relying on a 
static client set-of-ips for performance is really unpleasant, anyway. It would 
be a very strange scenario for users to discover that their database 
performance degrades over time for reasons unrelated to their load.

That all said, if we only promise to store (and deliver back to users) the 
_time_ component *_only_*, I think we can do it.


was (Author: benedict):
That is stale info, unfortunately :)

If we correct the risk of collision within a single application server, which 
is pretty essential, our LSB will suddenly explode regardless of how static our 
client set-of-ips is so optimising storage becomes impossible. And relying on a 
static client set-of-ips for performance is really unpleasant, anyway. It would 
be a very strange scenario for users to discover that their database 
performance degrades over time for reasons unrelated to their load.

That all said, if we promise to store (and deliver back to users) the _time_ 
component *_only_*, I think we can do it.

> Change timestamp representation to timeuuid
> -------------------------------------------
>
>                 Key: CASSANDRA-7919
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-7919
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: T Jake Luciani
>            Priority: Minor
>             Fix For: 3.0
>
>
> In order to overcome some of the issues with timestamps (CASSANDRA-6123) we 
> need to migrate to a better timestamp representation for cells.
> Since drivers already support timeuuid it makes sense to migrate to this 
> internally (see CASSANDRA-7056)



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

Reply via email to