hi, kylin team, 1. does a topk query scan all the data in the cube table? 2. does the order of the dimensions in rowkey effect the query speed? for example, a rowkey consists of A,B,C dimension in order, and will a query with "WHERE A=a" be finished faster than another with "WHERE C=c"? In my view, as the hbase table rows are sorting in the lexicographical order, and the former query will result in a partial scan with a rowkey scale from "a" to "aa", while the latter one will result in a full scan. But I don't know whether the hbase coprocessor will do anything to make the latter one efficient. I'd like to know how Kylin deals with it.
if I get anything wrong, I will appreciate any correction. thanks, Shon
