Hiļ¼all We have some questions about query across different model/cubes. We know that kylin will evaluate the cost and select the best cube to query. In our usage, this worked very good. But if we add more models with filter, the problem comes.
Here is our scenario, 2 model comes from the same fact table: table_A. Model test1 without any filter. cube1 with dimension A,B,C,D,E Model test1 with filter xxx = yyy. cube2 with dimension A If we query select count(1) from table_A; Kylin engine will route the query to cube2. But our target will be cube1. I wonder if we can specify the model when we make the query? Because if someone by mistake create a cube with overlaping dimension in a new model with filter conditions. It will impact others. In our usage, we temporarily limit only 1 model for 1 project. So, im sum, my question is: I wonder if we can specify the model when we make the query? Thanks. -- Yuxiang Mai
