[
https://issues.apache.org/jira/browse/CASSANDRA-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286155#comment-13286155
]
Hudson commented on CASSANDRA-4199:
-----------------------------------
Integrated in Cassandra #1467 (See
[https://builds.apache.org/job/Cassandra/1467/])
Add getsstables command to nodetool. Patch by Brandon Williams, reviewed by
yukim for CASSANDRA-4199 (Revision 5cda764a9f956c35feba0a4cf3138037fcf39a76)
Result = FAILURE
mor.yuki :
Files :
* src/java/org/apache/cassandra/db/ColumnFamilyStoreMBean.java
* CHANGES.txt
* src/java/org/apache/cassandra/tools/NodeProbe.java
* src/java/org/apache/cassandra/io/sstable/SSTableReader.java
* src/java/org/apache/cassandra/tools/NodeCmd.java
* src/java/org/apache/cassandra/db/ColumnFamilyStore.java
> 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
> Assignee: Brandon Williams
> Priority: Minor
> Fix For: 1.1.1
>
> Attachments: 4199-v2.txt, 4199.txt
>
>
> 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
