You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shao Feng Shi (Jira)" <ji...@apache.org> on 2020/05/27 10:03:00 UTC
[jira] [Closed] (KYLIN-700) Cube Release Tool
[ https://issues.apache.org/jira/browse/KYLIN-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shao Feng Shi closed KYLIN-700.
-------------------------------
> Cube Release Tool
> -----------------
>
> Key: KYLIN-700
> URL: https://issues.apache.org/jira/browse/KYLIN-700
> Project: Kylin
> Issue Type: New Feature
> Components: Tools, Build and Test
> Reporter: Luke Han
> Assignee: Hongbin Ma
> Priority: Major
>
> In real case, there's always different environment for user to develop, test and serve as production.
> To avoid rebuild same cubes on different environment, release verified/certified cubes from Dev/QA to Prod is more efficient way, and, this will support almost zero downtime when cube's data model changed (build first on QA and release to Prod)
> This tool will enable user to "release" cubes from one environment to another one:
> 1. Shell script is good enough so far
> 2. Service/Web GUI is nice to have
> 3. Only project admin/system admin could do this movement
> 4. Parameters:
> Source: Env(Host?)/Project/Cube
> Target: Env(Host?)/Project/Cube
> The target project/cube could be different name than source's
> 5. Support move metadata only and both metadata & data
> 6. Support rollback, for example, when the moving failed, the target cube should not be effected (keep as previous)
> 7. Log all actions for tracking
> Open question:
> 1. How to copy between different cluster for large cube?
> 2. Move or copy? Move will disable access from source, copy will ask more additional storage.
> Please leave your comments here.
> Thanks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)