[
https://issues.apache.org/jira/browse/KYLIN-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Zhichao Zhang 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:
!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.
*For this new feature, add some new properties*:
* kylin.cube.migration.enabled
Specifies whether to show 'Migrate', 'Approve Migration' and 'Reject Migration'
in "Action" drop-down list for cube management, the default value is false;
* kylin.metadata.model-schema-updater-checker-enabled
Specifies whether to check for model schema update when check check model
compatibility, the default value is false;
* kylin.metadata.able-change-string-to-datetime
Specifies whether to enable to convert String to Date or Time when check table
schema update, the default value is false;
* kylin.cube.rowkey-encoding-auto-convert
Specifies whether to enable to convert date/time dictionary on
date/time/varchar column to DimensionEncoding implicitly, the default value is
true;
* kylin.server.self-discovery-enabled
Specifies whether to enable to discover kylin instance from zookeeper, the
default value is false;
* kylin.cube.migration.expansion-rate
Specifies the threshold value of expansion rate when check the quality of the
cube, the default value is 5;
* kylin.cube.migration.query-generator-max-dimension-number
Specifies the max number of dimension column when generate sql for checking the
quality of the cube, the default value is 3;
* kylin.cube.migration.rule-query-latency-enabled
Specifies whether to check query latency when check the quality of the cube,
the default value is true;
* kylin.cube.migration.query-latency-seconds
Specifies the threshold value of query latency in seconds when check the
quality of the cube, the default value is 2;
* kylin.cube.migration.query-latency-max-threads
Specifies the max number of query threads to execute sql when check the quality
of the cube, the default value is 5;
* kylin.cube.migration.query-latency-iteration
Specifies the max number of query sql to be generated when check the quality of
the cube, the default value is 5;
* kylin.cube.migration.source-address
Specifies the source address of kylin instance;
* kylin.cube.migration.target-address
Specifies the target address of kylin instance;
* kylin.cube.notification-mail-suffix
Specifies the default suffix address of email for sending notifications.
was:
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.
> 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.
>
> *For this new feature, add some new properties*:
> * kylin.cube.migration.enabled
> Specifies whether to show 'Migrate', 'Approve Migration' and 'Reject
> Migration' in "Action" drop-down list for cube management, the default value
> is false;
> * kylin.metadata.model-schema-updater-checker-enabled
> Specifies whether to check for model schema update when check check model
> compatibility, the default value is false;
> * kylin.metadata.able-change-string-to-datetime
> Specifies whether to enable to convert String to Date or Time when check
> table schema update, the default value is false;
> * kylin.cube.rowkey-encoding-auto-convert
> Specifies whether to enable to convert date/time dictionary on
> date/time/varchar column to DimensionEncoding implicitly, the default value
> is true;
> * kylin.server.self-discovery-enabled
> Specifies whether to enable to discover kylin instance from zookeeper, the
> default value is false;
> * kylin.cube.migration.expansion-rate
> Specifies the threshold value of expansion rate when check the quality of the
> cube, the default value is 5;
> * kylin.cube.migration.query-generator-max-dimension-number
> Specifies the max number of dimension column when generate sql for checking
> the quality of the cube, the default value is 3;
> * kylin.cube.migration.rule-query-latency-enabled
> Specifies whether to check query latency when check the quality of the cube,
> the default value is true;
> * kylin.cube.migration.query-latency-seconds
> Specifies the threshold value of query latency in seconds when check the
> quality of the cube, the default value is 2;
> * kylin.cube.migration.query-latency-max-threads
> Specifies the max number of query threads to execute sql when check the
> quality of the cube, the default value is 5;
> * kylin.cube.migration.query-latency-iteration
> Specifies the max number of query sql to be generated when check the quality
> of the cube, the default value is 5;
> * kylin.cube.migration.source-address
> Specifies the source address of kylin instance;
> * kylin.cube.migration.target-address
> Specifies the target address of kylin instance;
> * kylin.cube.notification-mail-suffix
> Specifies the default suffix address of email for sending notifications.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
