[
https://issues.apache.org/jira/browse/KYLIN-3029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16264369#comment-16264369
]
Zhixiong Chen commented on KYLIN-3029:
--------------------------------------
Hi,[~peng.jianhua]
This issue is because the CubeService.list api is asynchronous.
However, the codes should in '$scope.check_cube_info' function.
So you could put the check exist cube code in CubeService.list api success
callback.
> The warning window of exist cube name is not work
> -------------------------------------------------
>
> Key: KYLIN-3029
> URL: https://issues.apache.org/jira/browse/KYLIN-3029
> Project: Kylin
> Issue Type: Bug
> Components: Web
> Affects Versions: v2.3.0
> Reporter: peng.jianhua
> Assignee: peng.jianhua
> Labels: scope
> Attachments:
> 0001-KYLIN-3029-The-warning-window-of-exist-cube-name-is-.patch, 01.PNG,
> 02.PNG, 03.PNG
>
>
> The dealing logical of the warning window of exist cube name is error. The
> issue can be reproduced using the following steps:
> Add a same name cube such as 'kylin_sales_cube', then click the 'next' button
> to enter a new page, we can't get the warning window.
> Click 'Prev' button in the page to return back to the first step,then click
> 'next' button again,we can get the warning window.
> Further if you keep editing the cube,you will get the error message like
> 01.png.
> It should like 02.png anyway.
> The 03.PNG shows that the code in 'cubeSchema.js' can check whether the cube
> name exists, but it's logical is error.
> The right dealing logical should be as following:
> The program should first check whether the cube exists when we clicked the
> "next" button.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
