You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2014/02/28 17:10:23 UTC
[jira] [Resolved] (CASSANDRA-6784) Compaction timestamp captured
incorrectly in Compaction History table
[ https://issues.apache.org/jira/browse/CASSANDRA-6784?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Ellis resolved CASSANDRA-6784.
---------------------------------------
Resolution: Fixed
Reviewer: Jonathan Ellis
Assignee: Chander S Pechetty
Since it's a cell of type timestamp (not an internal cell timestamp) it actually needs to be millis-since-epoch. This makes cqlsh happy. Committed w/ that change.
> Compaction timestamp captured incorrectly in Compaction History table
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-6784
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6784
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Reporter: Chander S Pechetty
> Assignee: Chander S Pechetty
> Priority: Trivial
> Labels: patch
> Fix For: 2.0.6
>
> Attachments: trunk-6784.txt
>
>
> Compaction finish time is incorrectly captured using System.nanoTime() before the compaction is triggered. The finish time should be captured using System.currentTimeMillis() as per #4432. The suggested patch captures using FBUtilities.timestampMicros() after the compaction completes.
>
> This however doesn't fix the formatting of timestamp values by
> cqlsh which throws decoding errors as below:
> - Failed to format value NNN.. as timestamp: timestamp out of range for platform time_t
>
> Reference : https://issues.apache.org/jira/browse/CASSANDRA-4432
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)