resolved, thanks! 2015-06-25 17:26 GMT+08:00 Li Yang <[email protected]>:
> Currently the only way to adjust cost is by export the cube's metadata, > make changes, and import back. > > Using the ResourceTool mentioned here > > https://github.com/apache/incubator-kylin/blob/master/docs/Operations/Kylin%20Metadata%20Store.md > > > On Thu, Jun 25, 2015 at 4:51 PM, dong wang <[email protected]> wrote: > > > "You may adjust cube's metadata directly." what does it mean? actually, > I > > have 2 cubes based on the same fact able, and which have been built > > successfully, then, can I manually change the cost for the cube we want > to > > select? > > > > 2015-06-25 16:43 GMT+08:00 Li Yang <[email protected]>: > > > > > IRealization.getCost() should return a meaningful value and QueryRouter > > > will choose a cheapest realization. > > > > > > Currently all cube's cost is 50 by default and not adjustable on GUI I > > > believe. You may adjust cube's metadata directly. > > > > > > When costs are equal, the cube with minimal dimensions and metrics will > > be > > > selected. > > > > > > > > > On Thu, Jun 25, 2015 at 4:35 PM, dong wang <[email protected]> > > wrote: > > > > > > > for the code: > > > org.apache.kylin.query.routing.QueryRouter.selectRealization > > > > > > > > if we have more than one suitable cube candidates, is it possible for > > > users > > > > to set some property such as weight under the "cube" tab on the web > for > > > > each cube to decide which cube is best to be selected manually? > > > > > > > > > >
