Hi Hongbin, Can you give a little bit detailed explanation for the cube selection algorithm? In a project, two cubes are created with the same data model. When I'd like to make a query, how does Kylin select the correct cube? Is there any possible that Kylin select a wrong cube (For example, the cube does not include the dimension that the query actually uses)?
Assuming we have a scenario that the whole dataset is pretty big, we cannot build the cube one time (from the start time to the end time of the dataset). So we decide to build the cube year by year, saying we built cubeA from 2014 to 2015 and cubeB from 2013 to 2014. When the query is about asking something from 2014 to 2015, does the selection algorithm select cubeA (2014 to 2015) correctly? What if the query is about asking something from 2013 to 2015? Should we do a merge of cubeA and cubeB? Is there a way to forcibly select a cube to use? Best regards, Zhong On Fri, Jan 22, 2016 at 2:53 AM, hongbin ma <[email protected]> wrote: > i see, so cube selection should honor cubes with a better rowkey order > respecting the current query. > > any other scenarios? > > -- > Regards, > > *Bin Mahone | 马洪宾* > Apache Kylin: http://kylin.io > Github: https://github.com/binmahone >
