cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksey Yeschenko (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-9505) Expose sparse formatting via JMX and/or sstablemetadata
Date Mon, 17 Aug 2015 17:03:45 GMT

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

Aleksey Yeschenko resolved CASSANDRA-9505.
------------------------------------------
    Resolution: Not A Problem

Agreed. This is a non-issue.

> Expose sparse formatting via JMX and/or sstablemetadata
> -------------------------------------------------------
>
>                 Key: CASSANDRA-9505
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9505
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jim Witschey
>             Fix For: 3.0.0 rc1
>
>
> It'd be helpful for us in TE if we could differentiate between data written in the sparse
and dense formats as described [here|https://github.com/pcmanus/cassandra/blob/8099/guide_8099.md#storage-format-on-disk-and-on-wire].
It'd help us to measure speed and space performance and to make sure the format is chosen
correctly and consistently.
> I don't know if this would be best exposed through a JMX endpoint, {{sstablemetadata}},
or both, but those seem like the most obvious exposure points.



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

Mime
View raw message