[
https://issues.apache.org/jira/browse/CASSANDRA-4432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410562#comment-13410562
]
Sylvain Lebresne commented on CASSANDRA-4432:
---------------------------------------------
I suppose that since we'll access the system table (including the schema)
directly in CQL3, it might be worth using micro-seconds.
> 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
