[
https://issues.apache.org/jira/browse/CASSANDRA-2168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002927#comment-13002927
]
Benjamin Coverston commented on CASSANDRA-2168:
-----------------------------------------------
I made a simpler change. All I did was make a sanity check to see if after
seeking the key matched the key we were looking for. If seek reached the end of
the list it would only deserialize the row if it is the one we are looking for,
otherwise it will continue to the next key in the for loop.
> SSTable2Json tool returns a different key when a querying for a specific key
> in an SSTable that does not exist
> --------------------------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-2168
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2168
> Project: Cassandra
> Issue Type: Bug
> Reporter: Benjamin Coverston
> Assignee: Benjamin Coverston
> Priority: Minor
> Fix For: 0.7.4
>
>
> bin/sstable2json storage/core/data/Foo/BAR-1-Data.db -k NonExistantKey
> returns
> { "ExistantKey" }
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
