[
https://issues.apache.org/jira/browse/KYLIN-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17111825#comment-17111825
]
ASF GitHub Bot commented on KYLIN-4485:
---------------------------------------
kyotoYaho opened a new pull request #1218:
URL: https://github.com/apache/kylin/pull/1218
## Proposed changes
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug or
resolves a feature request, be sure to link to that issue.
## Types of changes
What types of changes does your code introduce to Kylin?
_Put an `x` in the boxes that apply_
- [ ] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Documentation Update (if none of the other choices apply)
## Checklist
_Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look for
before merging your code._
- [ ] I have create an issue on [Kylin's
jira](https://issues.apache.org/jira/browse/KYLIN), and have described the
bug/feature there in detail
- [ ] Commit messages in my PR start with the related jira ID, like
"KYLIN-0000 Make Kylin project open-source"
- [ ] Compiling and unit tests pass locally with my changes
- [ ] I have added tests that prove my fix is effective or that my feature
works
- [ ] If this change need a document change, I will prepare another pr
against the `document` branch
- [ ] Any dependent changes have been merged
## Further comments
If this is a relatively large or complex change, kick off the discussion at
user@kylin or dev@kylin by explaining why you chose the solution you did and
what alternatives you considered, etc...
----------------------------------------------------------------
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:
[email protected]
> 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-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)
