On Tue, Feb 24, 2015 at 8:50 AM, Yulian Oifa <oifa.yul...@gmail.com> wrote:
> The structure is the same , the CFs are super column CFs , where key is > long ( timestamp to partition the index , so each 11 days new row is > created ) , super Column is int32 and columns / values are timeuuids.I am > running same queries , getting reversed slice by raw key and super column. > Obligatory notice that Super Columns are not really recommended for use. I have no idea if the performance problem you are seeing is related to the use of Super Columns. =Rob
