Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Thu, 26 Nov 2015 11:10:11 +0000 (UTC)
From: "Benjamin Lerer (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.12916394.1448531572000.201979.1448536210998@Atlassian.JIRA>
In-Reply-To: <JIRA.12916394.1448531572000@Atlassian.JIRA>
References: <JIRA.12916394.1448531572000@Atlassian.JIRA>
 <JIRA.12916394.1448531572382@arcas>
Subject: [jira] [Updated] (CASSANDRA-10775) SSTable compression ratio is not
 serialized properly
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CASSANDRA-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Lerer updated CASSANDRA-10775:
---------------------------------------
    Attachment: 10775-2.2.txt

The patch makes sure that the metadata are computed after the compression ratio addition.

Waiting for CI results

> SSTable compression ratio is not serialized properly
> ----------------------------------------------------
>
>                 Key: CASSANDRA-10775
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10775
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Local Write-Read Paths
>            Reporter: Benjamin Lerer
>            Assignee: Benjamin Lerer
>             Fix For: 3.0.x, 3.x
>
>         Attachments: 10775-2.2.txt
>
>
> While reviewing CASSANDRA-10225, I found out that the compression ratio returned by the {{StatsMetadata}} for some compressed sstables was - 1 (NO_COMPRESSION_RATIO). 
> After investigation it seems that the wrong compression ratio was serialized to disk. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)