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

Michael Theroux edited comment on CASSANDRA-4432 at 7/10/12 5:19 PM:
---------------------------------------------------------------------

Its a consideration for existing users.  Any user who would have created a 
keyspace before this fix, will have timestamps in whatever System.nanoTime() 
returns.  The bigger you make the timestamp, the less users will be stuck 
attempting to fix their timestamps so they can update their schema (I guess 
using sstable2json?).  Plus, its consistent with columns :)  
                
      was (Author: mtheroux2):
    However, any user who have created keyspaces will have timestamps in 
whatever System.nanoTime() returns.  The bigger you make the timestamp, the 
less users will be stuck attempting to fix their timestamps so they can update 
their schema (I guess using sstable2json?).  Plus, its consistent with columns 
:)  
                  
> Change nanoTime() to currentTimeInMillis() in schema related code.
> ------------------------------------------------------------------
>
>                 Key: CASSANDRA-4432
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4432
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.2
>            Reporter: Pavel Yaskevich
>            Assignee: Pavel Yaskevich
>             Fix For: 1.1.3
>
>         Attachments: CASSANDRA-4432.patch
>
>
> From nanoTime() description:
> "The value returned represents nanoseconds since some fixed but arbitrary 
> time (perhaps in the future, so values may be negative). This method provides 
> nanosecond precision, but not necessarily nanosecond accuracy. No guarantees 
> are made about how frequently values change."
> Also see http://www.mail-archive.com/[email protected]/msg04992.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to