[
https://issues.apache.org/jira/browse/CASSANDRA-4199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yuki Morishita updated CASSANDRA-4199:
--------------------------------------
Attachment: 4199-v2.txt
Since markReferenced(key) uses interval tree to search sstbales, you may get
unrelated sstables. If that is not intended, I uploaded patch to check if given
key is actually in referenced sstables by using SSTableReader#getPosition. Note
that getPosition updates key cache and bloom filter related stats, so I add
flag to turn off caching and stats update.
> 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
> Labels: lhf
> 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
