One of the reasons of using reverse order is to skip the tombstones while
doing a range query. Here is an example.
*
Lets say we want to read all the data which is between 10 minutes old upto
60 minute old. If the data is stored from old to new in an sstable, then we
have to go over all the tombst
On Wed, Jul 3, 2013 at 6:02 AM, Hiller, Dean wrote:
>
> We loaded 5 million columns into a single row and when accessing the
first 30k and last 30k columns we saw no performance difference. We tried
just loading 2 rows from the beginning and end and saw no performance
difference. I am sure rever
We loaded 5 million columns into a single row and when accessing the first 30k
and last 30k columns we saw no performance difference. We tried just loading 2
rows from the beginning and end and saw no performance difference. I am sure
reverse sort is there for a reason though. In what context
