[ 
https://issues.apache.org/jira/browse/KYLIN-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17130102#comment-17130102
 ] 

ASF GitHub Bot commented on KYLIN-4485:
---------------------------------------

lgtm-com[bot] commented on pull request #1218:
URL: https://github.com/apache/kylin/pull/1218#issuecomment-641741423


   This pull request **introduces 2 alerts** when merging 
dee7914c39d4d121dc5d6d9e8b7eb04dac75101b into 
12e4ad9786c6d6246c06731340f592f58325363e - [view on 
LGTM.com](https://lgtm.com/projects/g/apache/kylin/rev/pr-29afebfb366722978587276c57e3ae80b11e3399)
   
   **new alerts:**
   
   * 1 for Uncontrolled data used in path expression
   * 1 for Missing format argument


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Create a self service interface for cube migration
> --------------------------------------------------
>
>                 Key: KYLIN-4485
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4485
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Tools, Build and Test
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>            Priority: Major
>             Fix For: v3.1.0
>
>         Attachments: cube-migration-new.png, cube-migration-old.png
>
>
> Current cube migration process is as follows:
>   !cube-migration-old.png!
> There're a few drawbacks:
>  * kylin admin has to manually check all related aspects to decide whether a 
> cube is good for migration. If cube design is not good, there'll be many 
> interaction between users & kylin admins
>  * kylin admin has to login to the backend server and then run a command to 
> do the migration, which is tricky and easy to make mistakes
>  * there's little compatibility check between source metadata & destination 
> cluster.
> A self service interface will refine the migration process as follows:
> !cube-migration-new.png!
> We can see with the new migration process, there'll be few interactions 
> between users & kylin admins and much less work for kylin admins.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to