You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Marcus Eriksson (Jira)" <ji...@apache.org> on 2020/08/14 15:03:00 UTC

[jira] [Created] (CASSANDRA-16050) Handle difference in timestamp precision between java8 and java11 in LogFIle.java

Marcus Eriksson created CASSANDRA-16050:
-------------------------------------------

             Summary: Handle difference in timestamp precision between java8 and java11 in LogFIle.java
                 Key: CASSANDRA-16050
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-16050
             Project: Cassandra
          Issue Type: Bug
            Reporter: Marcus Eriksson
            Assignee: Marcus Eriksson


https://bugs.openjdk.java.net/browse/JDK-8177809 made File.lastModified include milliseconds while java8 always has them as 000.

This causes problems in LogFile.java where we compare the timestamps with what we have in the logfile: [LogFile.java|https://github.com/apache/cassandra/blob/ffc8e407e087e942c4e5c40605743fe3b32d8fd5/src/java/org/apache/cassandra/db/lifecycle/LogFile.java#L234]. This means that we can throw errors when changing between java11 and 8



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org