You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Brandon Williams (JIRA)" <ji...@apache.org> on 2012/04/30 22:43:49 UTC
[jira] [Updated] (CASSANDRA-4199) There should be an easy way to
find out which sstables a key lives in
[ https://issues.apache.org/jira/browse/CASSANDRA-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brandon Williams updated CASSANDRA-4199:
----------------------------------------
Labels: lhf (was: )
> There should be an easy way to find out which sstables a key lives in
> ---------------------------------------------------------------------
>
> Key: CASSANDRA-4199
> URL: https://issues.apache.org/jira/browse/CASSANDRA-4199
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Brandon Williams
> Labels: lhf
> Fix For: 1.1.1
>
>
> When debugging, often times on a live server you want to extract a certain key with sst2j, but unfortunately you can't know which sstable(s) you need to run this on, causing you to iterate over much more data than necessary.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira