[
https://issues.apache.org/jira/browse/KYLIN-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhong Yanghong updated KYLIN-4485:
----------------------------------
Description:
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:
was:
Current cube migration process is as follows:
Currently for cube migration, there're 3 drawbacks:
* kylin admin has to manually check all related aspects to decide whether a
cube is good for migration.
* kylin admin has to login to the backend server and then run a command.
* there's little compatibility check between source metadata & destination
cluster.
* there's no notification for users & admins to indicate whether the migration
succeeds or not.
A self service interface will refine the migration process as follows:
A self service interface brings following benefits:
* Some basic aspects can be checked
> 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
> Attachments: 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:
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
