Sure, in v1.x we assume one model map one cube, will remove the update code ,incase other cube's model updated.
and if cube create failed will rollback the model create. On Fri, Dec 25, 2015 at 5:50 PM, yu feng <[email protected]> wrote: > Yes, It solve this problem in web UI, However If I do not create cube in > web UI(such as curl command), the problem will happen again, I think you > should check whether cube name exist in CubeController(server side), then > update cube model ... > > 2015-12-25 17:38 GMT+08:00 Jian Zhong <[email protected]>: > > > we add CUBE_NAME check when create cube on UI,released in V1.2 > > > > https://issues.apache.org/jira/browse/KYLIN-966?filter=-1 > > > > > > On Fri, Dec 25, 2015 at 3:49 PM, Jian Zhong <[email protected]> > > wrote: > > > > > Good catch, > > > > > > I'll fix this. > > > > > > https://issues.apache.org/jira/browse/KYLIN-1254 > > > > > > On Fri, Dec 25, 2015 at 3:17 PM, yu feng <[email protected]> wrote: > > > > > >> Hi, I find a Bug like this in kylin-1.0: > > >> I build a cube named TEST successfully, and then build another cube > > named > > >> TEST too, those two cube has different fact table, the second cube > will > > be > > >> error becacuse "The cube named TEST already exists", But the model of > > >> first > > >> cube will be overridden. > > >> > > >> this is because kylin will save or update cube model before save a > cube. > > >> > > > > > > > > >
