cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mat Brown <>
Subject Key order check in sstable2json
Date Thu, 09 Aug 2012 14:14:19 GMT

We've noticed that when passing multiple -k arguments to the
sstable2json utility, we pretty much always get an IOException with
"Key out of order!". Looking at this:
it looks like it's iterating over the keys in the order given, and
then enforcing partitioner ordering of the keys. Is that correct? If
so, why? The original patch states that the key ordering check is to
detect corrupt sstables, and it does provide that benefit
where the check runs in the enumerateKeys method, but I don't see
any advantage to enforcing key order in the export method, other than
I suppose making scanning for the next key maximally efficient.

Anyway, with the current situation, it seems that the only way to pass
multiple key arguments to sstable2json would be to use sstablekeys
first to get the key order, grep for the keys I'm interested in, and
then pass those in order to sstable2json? Is this worth it, or would
it be comparably efficient to just call sstable2json on one key at a


View raw message