[
https://issues.apache.org/jira/browse/CASSANDRA-16050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Capwell updated CASSANDRA-16050:
--------------------------------------
Fix Version/s: (was: 3.11.x)
(was: 4.0)
(was: 3.0.x)
4.0-beta2
3.11.8
3.0.22
Since Version: 3.0.0
Source Control Link:
https://github.com/apache/cassandra/commit/c89f3df91139deee6fe78cc73a2ff0514c8af721
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
CI results:
3.0:
https://app.circleci.com/pipelines/github/dcapwell/cassandra/410/workflows/4cb109bf-d829-42ab-8f0e-b91c7c7969c4
3.11:
https://app.circleci.com/pipelines/github/dcapwell/cassandra/411/workflows/beb8e3b0-6102-4f7f-9bbb-743e99cef325
trunk:
https://app.circleci.com/pipelines/github/dcapwell/cassandra/412/workflows/3df9f8d3-512c-44a7-bfe2-5842c79542d0
There were failed tests, but all known flaky.
> 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
> Components: Local/SSTable, Local/Startup and Shutdown
> Reporter: Marcus Eriksson
> Assignee: Marcus Eriksson
> Priority: Normal
> Fix For: 3.0.22, 3.11.8, 4.0-beta2
>
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
