@Software Dev - if you use Phoenix, queries would leverage our Skip Scan
(which supports a superset of the FuzzyRowFilter perf improvements). Take a
Assuming a row key made up of a low cardinality first value (like a byte
representing an enum), followed by a high cardinality second value (like a
date/time value) you'd get a large benefit from the skip scan when you're
only looking a small sliver of your time range.
Another option would be to create a secondary index over your date:
On Sun, May 18, 2014 at 1:56 PM, James Taylor <[EMAIL PROTECTED]>wrote: